fix some typos

articles/post56.php

@@ -24,7 +24,7 @@
                             <li>Less modular</li>
                                 <p>By combining the compositor and window manager, you're slowly making the display stack less and less modular. The days of choosing your compositor and choosing your window manager are now gone. It's all one big program, meaning even if you avoid desktop environments you're still going to have one big program that does everything. This is just not the way forward if you ask me. I believe the main reason for this is "making the desktop easier for new users", but at this point the GNU/Linux community should give up on new users who aren't willing to learn our technology.</p>
                             <li>Window managers are so complex</li>
-                                <p>It is incredibly easy to make an X11 window manager, because again it's a window like any other. You really just need to create a window, read atoms and finally move/resize windows around. On Wayland you now also need to implement a compositor, which adds a lot of complexity and room for failure. Even one of the more minimal Wayland compsitors dwl, a dwm rewrite for Wayland has many more lines of code than the original dwm, because now you also need to do the compoiting yourself. Not to mention, if you're using a minimal compositor like dwl, you can't have fancy effects and a minimal window manager, that's just not possible anymore, at least as of now.</p>
+                                <p>It is incredibly easy to make an X11 window manager, because again it's a window like any other. You really just need to create a window, read atoms and finally move/resize windows around. On Wayland you now also need to implement a compositor, which adds a lot of complexity and room for failure. Even one of the more minimal Wayland compsitors dwl, a dwm rewrite for Wayland has many more lines of code than the original dwm, because now you also need to do the compositing yourself. Not to mention, if you're using a minimal compositor like dwl, you can't have fancy effects and a minimal window manager, that's just not possible anymore, at least as of now.</p>
                                 <p>This added complexity led to libraries like wlroots being created, and its slogan really says it all; "about 60,000 lines of code you were going to write anyway". However even with wlroots you still need to implement compositing, there's no way to have a separate compositor with your window manager.</p>
                             <li>No, a Wayland compositor is not a window like any other.</li>
                                 <p>As I said earlier, a window manager on X11 is a window like any other. The only difference is it's the first window spawned (root window), and it is responsible for creating, resizing and displaying all other windows, although this is technically not a requirement. This is good because you can for example <code>startx /usr/bin/firefox</code> and have an X11 session that runs Firefox. Nothing else, just Firefox. This goes for any graphical program such as your terminal emulator, text editor, Emacs, etc. On Wayland, this is not possible, because windows do not implement compositing whatsoever. They are only responsible for creating themselves.</p>

faq.php

@@ -19,7 +19,7 @@
                 <h3>Q: What about Discord?</h3>
                     <p>Back in 2021 through some time late 2022, I had a Discord server. I have since deleted it. While I do still have my Discord account, I rarely actually use it anymore. I don't want to use Discord because it is nonfree spyware, but as if that wasn't enough already the community is pretty much a combination of the worst people you could imagine. Matrix seems to keep out all these weirdo normies relatively well, so if you want to reach me, feel free to join the Matrix. Link is at home.</p>
                 <h3>Q: Insert any question about politics here</h3>
-                    <p>I want to keep this site politics free (outside of free software of course). While this may change in the future, I have decided to do this because politics really do not matter much anyway. That said though, I absolutely despite SJWs, and if you are one of those then I kindly ask you to leave, because we do not want your nonsense here.</p>
+                    <p>I want to keep this site politics free (outside of free software of course). While this may change in the future, I have decided to do this because politics really do not matter much anyway. That said though, I absolutely despise SJWs, and if you are one of those then I kindly ask you to leave, because I do not want your nonsense here.</p>
                 <h3>Q: Can I still read this blog if I use Microsoft Windows or some other spyware?</h3>
                     <p>This is not really a question, however I am tired of people "apologizing" to me for using nonfree software. If you wish to use Windows, and play Candy Crush while reading my blog then you can do so. I am not going to tell you what you can use, however I will definitely make software recommendations. Please do <strong>not</strong> consider this me forcing you to use the software. If you don't want to use it, don't.</p>
                 <h3>Q: Can I fork your software?</h3>

rss.xml

@@ -446,7 +446,7 @@
                             <li>Less modular</li>
                                 <p>By combining the compositor and window manager, you're slowly making the display stack less and less modular. The days of choosing your compositor and choosing your window manager are now gone. It's all one big program, meaning even if you avoid desktop environments you're still going to have one big program that does everything. This is just not the way forward if you ask me. I believe the main reason for this is "making the desktop easier for new users", but at this point the GNU/Linux community should give up on new users who aren't willing to learn our technology.</p>
                             <li>Window managers are so complex</li>
-                                <p>It is incredibly easy to make an X11 window manager, because again it's a window like any other. You really just need to create a window, read atoms and finally move/resize windows around. On Wayland you now also need to implement a compositor, which adds a lot of complexity and room for failure. Even one of the more minimal Wayland compsitors dwl, a dwm rewrite for Wayland has many more lines of code than the original dwm, because now you also need to do the compoiting yourself. Not to mention, if you're using a minimal compositor like dwl, you can't have fancy effects and a minimal window manager, that's just not possible anymore, at least as of now.</p>
+                                <p>It is incredibly easy to make an X11 window manager, because again it's a window like any other. You really just need to create a window, read atoms and finally move/resize windows around. On Wayland you now also need to implement a compositor, which adds a lot of complexity and room for failure. Even one of the more minimal Wayland compsitors dwl, a dwm rewrite for Wayland has many more lines of code than the original dwm, because now you also need to do the compositing yourself. Not to mention, if you're using a minimal compositor like dwl, you can't have fancy effects and a minimal window manager, that's just not possible anymore, at least as of now.</p>
                                 <p>This added complexity led to libraries like wlroots being created, and its slogan really says it all; "about 60,000 lines of code you were going to write anyway". However even with wlroots you still need to implement compositing, there's no way to have a separate compositor with your window manager.</p>
                             <li>No, a Wayland compositor is not a window like any other.</li>
                                 <p>As I said earlier, a window manager on X11 is a window like any other. The only difference is it's the first window spawned (root window), and it is responsible for creating, resizing and displaying all other windows, although this is technically not a requirement. This is good because you can for example <code>startx /usr/bin/firefox</code> and have an X11 session that runs Firefox. Nothing else, just Firefox. This goes for any graphical program such as your terminal emulator, text editor, Emacs, etc. On Wayland, this is not possible, because windows do not implement compositing whatsoever. They are only responsible for creating themselves.</p>