Lint fixes

Signed-off-by: Ian Maddaus <[email protected]>

Author: IanMadd

content/habitat/builder/on_prem/configure/disaster_recovery_warm_spare.md

@@ -20,7 +20,7 @@ There's no fully on-premises solution for highly available Habitat Builder servi
 
 The following architecture diagram shows how data synchronization increases the availability of the Builder API and backend for disaster recovery and warm spare scenarios.
 
-![Habitat On-Prem Builderises architecture](/habitat/builder/on_prem/builder_architecture.png)
+![Habitat On-Prem Builder's architecture](/habitat/builder/on_prem/builder_architecture.png)
 
 ### Synchronize components
 

content/habitat/builder/on_prem/configure/scale_frontend_nodes.md

@@ -56,7 +56,7 @@ Because Habitat Builder services need to communicate across your network between
 
 ## Create a Builder config file
 
-The `bldr.env` file for your single On-Prem Builder node contains most of the information you need to bootstrap a new frontend and is used to configure Builder durin installation.
+The `bldr.env` file for your single On-Prem Builder node contains most of the information you need to bootstrap a new frontend and is used to configure Builder during installation.
 
 1. On each node that you plan run as a frontend node, clone the [habitat-sh/on-prem-builder repository](https://github.com/habitat-sh/) or download and extract an [on-prem-builder release](https://github.com/habitat-sh/on-prem-builder/releases).
 

content/habitat/builder/on_prem/manage/postgres.md

@@ -9,6 +9,8 @@ title = "Manage Habitat Builder data stored by PostgreSQL"
     weight = 30
 +++
 
+<!--cspell:ignore createdb -->
+
 This page describes how to back up Habitat Builder user and package data that's managed by PostgreSQL.
 
 ## Habitat Builder data overview

content/habitat/builder/on_prem/origins/origin_keys.md

@@ -132,7 +132,7 @@ hab origin key download <ORIGIN>
 
 ### Upload origin keys with the CLI
 
-Creating an origin with the `hab origin create` command registers the origin on Chef Habitat On-prem Builder without creating an origin key pair. The `hab origin key generate` command creates the key pair and saves them in your local environment, but it does not upload either origin key to Chef Habitat On-prem Builder.
+Creating an origin with the `hab origin create` command registers the origin on Chef Habitat On-prem Builder without creating an origin key pair. The `hab origin key generate` command creates the key pair and saves them in your local environment, but it doesn't upload either origin key to Chef Habitat On-prem Builder.
 
 - Only origin members with the administrator and owner roles can upload new keys to an origin.
 - Habitat On-prem Builder requires the public origin key to upload artifacts for that origin, so you'll need to upload it.

content/habitat/builder/on_prem/troubleshooting.md

@@ -90,7 +90,7 @@ If self-signed certificates are missing, verify the following:
 
 - If your self-signed certificates are missing, copy them into the `/hab/cache/ssl` directory. The latest version of Chef Habitat On-Prem Builder expects certificates in that directory.
 
-- Name your certificate files using the pattern `appname-cert.cert` or `appname-cert.pem`. For example, `automate-cert.cert` or `automate-cert.pem`.
+- Name your certificate files using the pattern `<APP_NAME>-cert.cert` or `<APP_NAME>-cert.pem`. For example, `automate-cert.cert` or `automate-cert.pem`.
 
 - Don't use `cert.pem`, which is reserved for the Chef Habitat system.
    If you overwrite this file, Chef Habitat On-Prem Builder will fail.
@@ -211,7 +211,7 @@ HAB_CLIENT_SOCKET_TIMEOUT=360 hab pkg upload -u <BLDR_URL> -z <AUTH_TOKEN> <HART
 
 ### Package shows up in the Builder UI and `hab pkg search`, but `hab pkg install` fails
 
-If you run into a situation where you have a package populated in the Chef Habitat On-Prem Builder, but it is failing to install with a `Not Found` status, it is possible that there was a prior problem with populating the MinIO backend with the package artifact.
+If you run into a situation where you have a package populated in the Chef Habitat On-Prem Builder, but it's failing to install with a `Not Found` status, it's possible that there was a prior problem with populating the MinIO backend with the package artifact.
 
 If you have the package artifact on-disk (for example, in the `hab/cache/artifacts` directory), you can try to upload the missing package again with the following command (update the parameters as appropriate):