Minor edits.

.emacs.d/docs/faq.org

@@ -104,7 +104,7 @@ It does, /but/ there are caveats:
   pioneers, willing to test Doom on Windows.
 
 That said, Doom does have happy Windows users (using WSL or scoop/chocolatey).
-The [[file:getting_started.org::On Windows][Getting Starting guide]] will walk you through what we know.
+[[file:getting_started.org::On Windows][The Getting Starting guide]] will walk you through what we know.
 
 Help us improve our documentation if you managed to get Doom running on Windows!
 
@@ -340,8 +340,9 @@ Emacs consults this variable every time a file is read or library loaded, or
 when certain functions in the file API are used (like ~expand-file-name~ or
 ~file-truename~).
 
-Emacs does to check if a special handler is needed to read that file, but none
-of them are (typically) necessary at startup, so we disable them (temporarily!):
+Emacs does this to check if a special handler is needed to read that file, but
+none of them are (typically) necessary at startup, so we disable them
+(temporarily!):
 
 #+BEGIN_SRC emacs-lisp
 (defvar doom--file-name-handler-alist file-name-handler-alist)
@@ -527,7 +528,7 @@ This directory is referred to as your ~$DOOMDIR~.
 Your private config is typically comprised of an =init.el=, =config.el= and
 =packages.el= file. Put all your config in =config.el=, install packages by
 adding ~package!~ declarations to =packages.el=, and enable/disable modules in
-you ~doom!~ block, which should have been created in your =init.el= when you
+your ~doom!~ block, which should have been created in your =init.el= when you
 first ran ~doom install~.
 
 You shouldn't need to fork Doom or modify =~/.emacs.d=. If you have to do this

.emacs.d/docs/getting_started.org

@@ -311,13 +311,13 @@ process.
 Before moving on to installing Emacs et co, a few steps to prepare Windows for
 Emacs are necessary:
 
-1. *Create a ~HOME~ [[https://mywindowshub.com/how-to-edit-system-environment-variables-for-a-user-in-windows-10/][system environment variable]].*
+1. Create a ~HOME~ [[https://mywindowshub.com/how-to-edit-system-environment-variables-for-a-user-in-windows-10/][system environment variable]].
   
    Set it to =C:\Users\USERNAME\=, otherwise Emacs will treat
    =C:\Users\USERNAME\AppData\Roaming= as your ~HOME~, which will cause issues
    later.
 
-2. *Add =C:\Users\USERNAME\.emacs.d\bin= to your ~PATH~.*
+2. Add =C:\Users\USERNAME\.emacs.d\bin= to your ~PATH~.
 
    This way, you don't have to type all of =C:\Users\USERNAME\.emacs.d\bin\doom=
    every time you need to run this script (and you'll need to, often).
@@ -1068,8 +1068,7 @@ Of course, an empty module isn't terribly useful, but it goes to show that nothi
   loaded when they are used.
 
 These are a few exceptional examples of a well-rounded module:
-
-+ [[file:/mnt/projects/conf/doom-emacs/modules/completion/company/README.org][:completion company]]
++ [[file:../modules/completion/company/README.org][:completion company]]
 
 The remainder of this guide will go over the technical details of a Doom module.