diff --git a/basis/furnace/auth/auth-docs.factor b/basis/furnace/auth/auth-docs.factor
index 45bcb8a0ec..58317ee29a 100644
--- a/basis/furnace/auth/auth-docs.factor
+++ b/basis/furnace/auth/auth-docs.factor
@@ -121,7 +121,6 @@ $nl
     "furnace.auth.providers.null"
     "furnace.auth.providers.assoc"
     "furnace.auth.providers.db"
-    "furnace.auth.providers.couchdb"
 } ;
 
 ARTICLE: "furnace.auth.features" "Optional authentication features"
diff --git a/basis/furnace/auth/providers/couchdb/couchdb-docs.factor b/basis/furnace/auth/providers/couchdb/couchdb-docs.factor
index ec967f29d9..7481b7ac93 100644
--- a/basis/furnace/auth/providers/couchdb/couchdb-docs.factor
+++ b/basis/furnace/auth/providers/couchdb/couchdb-docs.factor
@@ -25,12 +25,12 @@ HELP: couchdb-auth-provider
 
 ARTICLE: "furnace.auth.providers.couchdb" "CouchDB Authentication Provider"
     "The " { $vocab-link "furnace.auth.providers.couchdb" } " vocabulary implements an authentication provider "
-    "which looks up authentication requests in a CouchDB. It is necessary to create a view "
+    "which looks up authentication requests in CouchDB. It is necessary to create a view "
     "associating usernames with user documents before using this vocabulary; see documentation "
     "for " { $link couchdb-auth-provider } "."
     $nl
     "Although this implementation guarantees that users with duplicate IDs/emails"
-    " cannot be created in a single CouchDB database, it provides so such guarentee if you are clustering "
+    " cannot be created in a single CouchDB database, it provides no such guarantee if you are clustering "
     "multiple DBs. In this case, you are responsible for ensuring the uniqueness of users across "
     "databases."
     $nl