Fix spelling errors found in the documentation (#1073)

website/content/docs/getting-started/connect-to-target.mdx

@@ -180,5 +180,5 @@ details.
 
 ## Next Steps
 
-See our [common workflows](/docs/common-workflows) for in depth discussion on managing scopes, targets,
+See our [common workflows](https://learn.hashicorp.com/collections/boundary/common-workflows) for in depth discussion on managing scopes, targets,
 identities, and sessions.

website/content/docs/getting-started/installing/production.mdx

@@ -217,7 +217,7 @@ sudo chown boundary:boundary /etc/${NAME}-${TYPE}.hcl
 sudo chown boundary:boundary /usr/local/bin/boundary
 
 # Make sure to initialize the DB before starting the service. This will result in
-# a database already initizalized warning if another controller or worker has done this
+# a database already initialized warning if another controller or worker has done this
 # already, making it a lazy, best effort initialization
 if [ "${TYPE}" = "controller" ]; then
   sudo /usr/local/bin/boundary database init -config /etc/${NAME}-${TYPE}.hcl || true

website/content/docs/getting-started/run-and-login.mdx

@@ -34,7 +34,7 @@ an error indicating that the token could not be stored, as the freedesktop.org
 Secret Service implementation is not always available. On these systems, you can
 work around this by installing `dbus-x11` and `gnome-keyring` using your package
 manager, then creating and unlocking the default keyring with the following,
-substituting in a password of your choice for "foorbar" (but ending with `\n`).
+substituting in a password of your choice for "foobar" (but ending with `\n`).
 You can also avoid putting the password on the command line by running the
 `gnome-keyring-daemon` commands directly and entering in the password, followed
 by a newline (return) and an EOF (`Ctrl+D`).