Gh-pages

docs/misconceptions.md

@@ -144,7 +144,7 @@ You can, of course, do things differently, but I would recommend the following a
 3.  **[IF RELEVANT] Set up your text editor/IDE to use the build tools.**
     *   If you use a text editor like VS Code, [vim](https://www.vim.org/), [Notepad++](https://notepad-plus-plus.org/), or any of the hundreds of others, you will need to set it up to use the build tools. Often you do this by installing the relevant extensions in your editor. Look up a tutorial online for configuring this.
     *   If you installed an IDE like [Visual Studio](https://visualstudio.com/) or one of the [JetBrains IDEs](https://www.jetbrains.com/products/) instead, it will likely have done this for you. If not, look up a tutorial online for configuring it.
-4.  **Make projects in folders, not files.** This is a good habit to get into, and will help you keep your code organized. It will also help you if you ever need to use a build system like [Make](https://www.gnu.org/software/make/) or [source control tools](https://eccentricorange.github.io/CAIE-Computer-Science/things-to-know.html#source-control). I recommend you make a folder for each project, and put all the files for that project in that folder. This includes your source code, any libraries you use, and any build files. This is a good habit to get into, and will help you keep your code organized. Additionally, most IDEs/editors are designed with larger projects in mind, and will work better if you use them this way.
+4.  **Make projects in folders, not files.** This is a good habit to get into, and will help you keep your code organized. It will also help you if you ever need to use a build system like [Make](https://www.gnu.org/software/make/) or [source control tools](https://eccentricorange.github.io/CAIE-Computer-Science/things-to-know.html#source-control). I recommend you make a folder for each project, and put all the files for that project in that folder. This includes your source code, any libraries you use, and any build files. Additionally, most IDEs/editors are designed with larger projects in mind, and will work better if you use them this way.
 
 <details markdown="1">
 <summary>Exceptions</summary>

docs/tools.md

@@ -49,7 +49,7 @@ While Git is exceedingly popular, you should know that there are alternatives, s
 Linus Torvalds visits Google to share his thoughts on git, the source control management system he created.
 
 ## 2.   Docker, for isolating your development environment
-[Dependency hell](https://en.wikipedia.org/wiki/Dependency_hell) is a problem that arises when you have multiple projects that depend on different versions of the same library, operating systems, or other software. For example, you might have one project that depends on version 1.0 of a library, and another that depends on version 2.0. If you install both of these on your computer, you'll run into problems, because the two versions of the library might not be compatible with each other. In fact, you may not be able to install them together in the first place.
+[Dependency hell](https://en.wikipedia.org/wiki/Dependency_hell) is a problem that arises when you have multiple projects that depend on different versions of the same library, different operating systems, or otherwise different systems. For example, you might have one project that depends on version 1.0 of a library, and another that depends on version 2.0. If you install both of these on your computer, you'll run into problems, because the two versions of the library might not be compatible with each other. In fact, you may not be able to install them together in the first place.
 
 ![Dependency hell, xkcd 1579](https://imgs.xkcd.com/comics/tech_loops.png)
 
@@ -61,7 +61,19 @@ FROM ubuntu:22.04
 
 There are many more options, such as different OSes, images with certain toolchains built-in, lightweight ones et cetera. You can check out the [Docker Registry](https://hub.docker.com/) for a complete listing.
 
-Crucially, whenever you start from a certain image, so does everyone else using your "Dockerfile". This means that you can be sure that everyone is starting from the same point, and that everyone has the same environment. This is great for reproducibility, and for making sure that your code works on other people's computers.
+Crucially, whenever you start from a certain environment (image), so does everyone else using your "Dockerfile". This means that you can be sure that everyone is starting from the same point, and that everyone has the same environment. This is great for reproducibility, and for making sure that your code works on other people's computers.
+
+<details markdown="1">
+
+<summary>Docker vs Virtual Machines</summary>
+
+On the surface, Docker containers behave like virtual machines. But Docker containers share the same kernel as the host system, which means that they are more lightweight than virtual machines.
+
+Read more:
+*   [From official Docker documentation](https://www.docker.com/resources/what-container)
+*   [_How is Docker different from a virtual machine?_ on Stack Overflow](https://stackoverflow.com/questions/16047306/how-is-docker-different-from-a-virtual-machine)
+
+</details>
 
 ### Resources to understand what Docker is
 *   [Official Docker documentation](https://docs.docker.com/get-started/overview/)