Fix spelling errors found in the documentation (#1073)

website/content/docs/installing/high-availability.mdx

@@ -30,7 +30,7 @@ needs:
 ![](/img/production.png)
 
 As shown above, Boundary is broken up into its controller and worker server components across 3 [EC2 instances](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance), in
-3 separate [subnets](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/subnet), in three separate [availability zones](), with the controller API and UI being publically exposed by an [application load balancer (ALB)](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb). The worker and controller VM's are in independant [auto-scaling groups](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group), allowing them to maintain their exact capacity.
+3 separate [subnets](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/subnet), in three separate [availability zones](), with the controller API and UI being publically exposed by an [application load balancer (ALB)](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb). The worker and controller VM's are in independent [auto-scaling groups](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group), allowing them to maintain their exact capacity.
 
 The workers must be able to establish a connection to the hosts with which they interact. In the architecture above, we place them in the public subnet so our remote client can establish a session between them and the target VM.
 

website/content/docs/installing/no-gen-resources.mdx

@@ -11,7 +11,7 @@ What are generated resources? When you run `boundary dev` or `boundary database
 generates a number of resources to make getting started easier. Default scopes, auth methods, user, account, and
 targets are just some of the resources Boundary will generate unless you tell it not to.
 
-In a production or long-running environment, these resoures are not neccessary, but without them, managing
+In a production or long-running environment, these resources are not necessary, but without them, managing
 Boundary from scratch isn't straight forward. How do you create your first user and login to administer a Boundary
 deployment that has no authentication methods, users, accounts, etc? This section describes how to get your freshly
 deployed Boundary installation off the ground for non-dev environments.

website/content/docs/installing/systemd.mdx

@@ -79,7 +79,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