some tone fixes. Not all warnings addressed

docs/guides/hosting/self-managed/aws-tf.md

@@ -8,11 +8,9 @@ displayed_sidebar: default
 W&B recommends fully managed deployment options such as [W&B Multi-tenant Cloud](../hosting-options/saas_cloud.md) or [W&B Dedicated Cloud](../hosting-options//dedicated_cloud.md) deployment types. W&B fully managed services are simple and secure to use, with minimum to no configuration required.
 :::
 
-W&B recommends using the [W&B Server AWS Terraform Module](https://registry.terraform.io/modules/wandb/wandb/aws/latest) to deploy the platform on AWS.
+W&B recommends using the [W&B Server AWS Terraform Module](https://registry.terraform.io/modules/wandb/wandb/aws/latest) to deploy the platform on AWS. 
 
-The module documentation is extensive and contains all available options that can be used. We will cover some deployment options in this document.
-
-Before you start, we recommend you choose one of the [remote backends](https://developer.hashicorp.com/terraform/language/settings/backends/configuration) available for Terraform to store the [State File](https://developer.hashicorp.com/terraform/language/state).
+Before you start, W&B recommends that you choose one of the [remote backends](https://developer.hashicorp.com/terraform/language/backend) available for Terraform to store the [State File](https://developer.hashicorp.com/terraform/language/state).
 
 The State File is the necessary resource to roll out upgrades or make changes in your deployment without recreating all components.
 
@@ -34,7 +32,7 @@ Other deployment options can also include the following optional components:
 - Elastic Cache for Redis
 - SQS
 
-## **Pre-requisite permissions**
+## Pre-requisite permissions
 
 The account that runs Terraform needs to be able to create all components described in the Introduction and permission to create **IAM Policies** and **IAM Roles** and assign roles to resources.
 
@@ -44,7 +42,7 @@ The steps on this topic are common for any deployment option covered by this doc
 
 1. Prepare the development environment.
    - Install [Terraform](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli)
-   - We recommend creating a Git repository with the code that will be used, but you can keep your files locally.
+   - W&B recommend creating a Git repository for version control.
 2. Create the `terraform.tfvars` file.
 
    The `tvfars` file content can be customized according to the installation type, but the minimum recommended will look like the example below.
@@ -87,7 +85,7 @@ The steps on this topic are common for any deployment option covered by this doc
 
    Refer to the [Terraform Official Documentation](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#provider-configuration) to configure the AWS provider.
 
-   Optionally, **but highly recommended**, add the [remote backend configuration](https://developer.hashicorp.com/terraform/language/settings/backends/configuration) mentioned at the beginning of this documentation.
+   Optionally, but highly recommended, add the [remote backend configuration](https://developer.hashicorp.com/terraform/language/settings/backends/configuration) mentioned at the beginning of this documentation.
 
 4. Create the file `variables.tf`
 
@@ -132,7 +130,7 @@ The steps on this topic are common for any deployment option covered by this doc
    }
    ```
 
-## Recommonded deployment option
+## Recommended deployment option
 
 This is the most straightforward deployment option configuration that creates all `Mandatory` components and installs in the `Kubernetes Cluster` the latest version of `W&B`.
 
@@ -184,8 +182,8 @@ This is the most straightforward deployment option configuration that creates al
      bucket_queue               = "internal://"
      database_connection_string = "mysql://${module.wandb_infra.database_connection_string}"
 
-     # If we dont wait, tf will start trying to deploy while the work group is
-     # still spinning up
+     # TF attempts to deploy while the work group is
+     # still spinning up if you do not wait
      depends_on = [module.wandb_infra]
    }
 
@@ -211,7 +209,7 @@ This is the most straightforward deployment option configuration that creates al
 
 Another deployment option uses `Redis` to cache the SQL queries and speed up the application response when loading the metrics for the experiments.
 
-You need to add the option `create_elasticache_subnet = true` to the same `main.tf` file we worked on in `Recommended Deployment` to enable the cache.
+You need to add the option `create_elasticache_subnet = true` to the same `main.tf` file described in the [Recommended deployment](#recommended-deployment-option) section to enable the cache.
 
 ```
 module "wandb_infra" {
@@ -231,7 +229,7 @@ module "wandb_infra" {
 
 Deployment option 3 consists of enabling the external `message broker`. This is optional because the W&B brings embedded a broker. This option doesn't bring a performance improvement.
 
-The AWS resource that provides the message broker is the `SQS`, and to enable it, you will need to add the option `use_internal_queue = false` to the same `main.tf` that we worked on the `Recommended Deployment`
+The AWS resource that provides the message broker is the `SQS`, and to enable it, you will need to add the option `use_internal_queue = false` to the same `main.tf` described in the [Recommended deployment](#recommended-deployment-option) section.
 
 ```
 module "wandb_infra" {
@@ -259,7 +257,7 @@ To use an Amazon S3 bucket as a file storage backend for W&B, you will need to:
 
 * [Create an Amazon S3 Bucket and Bucket Notifications](#create-an-s3-bucket-and-bucket-notifications)
 * [Create SQS Queue](#create-an-sqs-queue)
-* [Grant Permissions to Node Running W&B](#grant-permissions-to-node-running-wb)
+* [Grant Permissions to Node Running W&B](#grant-permissions-to-node-that-runs-wb)
 
 
  you'll need to create a bucket, along with an SQS queue configured to receive object creation notifications from that bucket. Your instance will need permissions to read from this queue.
@@ -347,7 +345,7 @@ The node where W&B server is running must be configured to permit access to Amaz
 }
 ```
 
-### Configure a W&B server
+### Configure W&B server
 Finally, configure your W&B Server.
 
 1. Navigate to the W&B settings page at `http(s)://YOUR-W&B-SERVER-HOST/system-admin`. 
@@ -380,7 +378,7 @@ Follow the steps outlined here to update W&B:
   Alternatively, you can add the `wandb_version` to the `terraform.tfvars` and create a variable with the same name and instead of using the literal value, use the `var.wandb_version`
   :::
 
-2. After you update your configuration, complete the steps described in the [Deployment section](#deployment---recommended-20-mins).
+2. After you update your configuration, complete the steps described in the [Recommended deployment section](#recommended-deployment-option).
 
 ## Migrate to operator-based AWS Terraform modules