diff --git a/docs/FAQ b/docs/FAQ
index 8b5e741d0..7f087fccc 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -141,7 +141,7 @@ A: Submit it on Sourceforge through our Sourceforge project page:
    (basically the stuff from "Uncaught exception in ..." to the next
    log entry).  We'd also like to see the commands that caused the
    bug, or happened around the time you saw the bug.  If the bug
-   involved a datase, we'd love to see the database.  Remember, it's
+   involved a database, we'd love to see the database.  Remember, it's
    always worse to send us too much information in a bug report than
    too little.
 
diff --git a/docs/GETTING_STARTED b/docs/GETTING_STARTED
index 269bc16bf..af94b9d4e 100644
--- a/docs/GETTING_STARTED
+++ b/docs/GETTING_STARTED
@@ -83,11 +83,12 @@ supybot: config list
 
 Rather than just "list".
 
-Speaking of the load command, that's the command you'll use to load
-other plugins.  If you didn't use supybot-wizard, though, you might do
-well to try it before playing around with loading plugins yourself:
-each plugin has its own configure function that the wizard uses to
-setup the appropriate registry entries if the plugin requires any.
+Now that you know how to deal with plugins having commands with the
+same name, let's take a look at loading other plugins.  If you didn't
+use supybot-wizard, though, you might do well to try it before playing
+around with loading plugins yourself: each plugin has its own
+configure function that the wizard uses to setup the appropriate
+registry entries if the plugin requires any.
 
 Now, if you do want to play around with loading plugins, you're going
 to need to have the owner capability.  If you ran the wizard, then