furnance.auth: fix documentation

The docs were attempting to reference the CouchDB auth provider, but
that fails, because the help vocab didn't include furnance.auth.couchdb.
Since the CouchDB auth vocab has some pretty serious caveats (see its
docs), remove it entirely for now.

Also fixes two minor typos in the furnace.auth.couchdb docs.

diff --git a/basis/furnace/auth/auth-docs.factor b/basis/furnace/auth/auth-docs.factor
index 45bcb8a0ec27a8bd316cd48526583b633f803c7f..58317ee29a2643d8dbce22430c7968ecf18d3eba 100644 (file)
--- 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 ec967f29d91ca7e4564bdb1d2e7a1ff081b25731..7481b7ac937e83be9af4ca372327ac9cebcada44 100644 (file)
--- 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