Automate HA Document Fixes (#8814)

* minor changes to ha docs

Signed-off-by: Dishank Tiwari <[email protected]>

* minor fixes

Signed-off-by: Dishank Tiwari <[email protected]>

* fixes indentation

Signed-off-by: Dishank Tiwari <[email protected]>

* review fixes

Signed-off-by: Dishank Tiwari <[email protected]>

* final fixes

Signed-off-by: Dishank Tiwari <[email protected]>

* review changes

Signed-off-by: Dishank Tiwari <[email protected]>

* Editing

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

* minor fixes

Signed-off-by: Dishank Tiwari <[email protected]>

* updated the docs

Signed-off-by: Dishank Tiwari <[email protected]>

* added the content fixes again

Signed-off-by: Dishank Tiwari <[email protected]>

* fixed changes

Signed-off-by: Dishank Tiwari <[email protected]>

---------

Signed-off-by: Dishank Tiwari <[email protected]>
Signed-off-by: Ian Maddaus <[email protected]>
Co-authored-by: Ian Maddaus <[email protected]>

Author: dishanktiwari2501

components/docs-chef-io/content/automate/ha.md

@@ -28,7 +28,7 @@ The Chef Automate HA equates to reliability, efficiency, and productivity, built
 
 HA architecture includes the cluster of the *Chef Automate*, *Chef Server*, *PostgreSQL*, and *OpenSearch*.
 
-### Chef Automate HA Architecture for OnPremise / Cloud Non-Managed
+### Chef Automate HA Architecture for On Premises / Cloud Non-Managed
 
 ![High Availability Architecture](/images/automate/ha_arch_onprem.png)
 
@@ -40,7 +40,9 @@ HA architecture includes the cluster of the *Chef Automate*, *Chef Server*, *Pos
 Chef Automate HA for Managed Services has default port 5432 for Managed PostgreSQL and 9200 for Managed OpenSearch. You can also change to your custom port.
 {{< /note >}}
 
-### Chef Automate HA Architecture for OnPremise Non-Managed Minimum Node Cluster
+### Chef Automate HA Architecture for On-Premises Non-Managed Minimum Node Cluster
+
+The following shows a five-node cluster, which is a supported deployment pattern. Work with your Progress technical teams to determine the appropriate cluster configuration for optimal performance based on parameters such as node count and data size.
 
 ![High Availability Architecture](/images/automate/ha_arch_minnode_cluster.png)
 
@@ -67,38 +69,39 @@ The Chef Automate HA Architecture involves the following clusters as part of the
 
 ## Provisioning
 
-Chef Automate's high availability solution can run on cloud providers and on-premise infrastructure systems. Appropriately provisioned backend, frontend, and bastion systems will help ensure a smooth deployment and installation experience.
+Chef Automate's high availability solution can run on cloud providers and on-premises infrastructure systems. Appropriately provisioned backend, frontend, and bastion systems ensure a smooth deployment and installation experience.
 
-  - On-premise provisioning
-  - Cloud provisioning
+- On-premises provisioning
+- Cloud provisioning
 
-### On-premise provisioning
+### On-premises provisioning
 
   The customer can provision virtual machines or bare metal machines on a supported operating system with the required system settings to deploy the Automate HA solution.
 
-### Cloud provisioing
-  Systems and services from the following cloud providers are supported:
+### Cloud provisioning
+
+Systems and services from the following cloud providers are supported:
 
-  - [AWS](https://docs.chef.io/automate/ha_aws_deploy_steps/#steps-to-provision)
-  - Azure
-  - Google
+- [AWS](https://docs.chef.io/automate/ha_aws_deploy_steps/#steps-to-provision)
+- Azure
+- Google
 
 Deploy the Automate HA on the cloud infrastructure after provisioning the cloud systems. We have a simplified provisioning utility for AWS, Azure, and Google, and we expect to provision the systems manually.
 
 ## Deployment Methods
 
 Chef Automate High Availability (HA) supports two types of deployment:
 
-- [On-premise Deployment (Existing Node) Deployment](/automate/ha_onprim_deployment_procedure/)
+- [on-premises Deployment (Existing Node) Deployment](/automate/ha_onprim_deployment_procedure/)
 - [Amazon Web Services (AWS) Deployment](/automate/ha_aws_deploy_steps/)
 
-### On-premise Deployment (Existing Node/Bare Infrastructure)
+### On-premises Deployment (Existing Node/Bare Infrastructure)
 
 In this, we expect VM (Virtual machine) or Bare Metal machines (Physical machine) that are already created and have initial Operating System (OS) setup done. Including Ports and Security policies changed according to requirements.
 
 After this, installation steps will Deploy Chef Automate, Chef Infra Server, PostgreSQL DB, and OpenSearch DB to the relevant VMs or Physical Machines as provided in Config.
 
-Please refer [Performance Bench marking](https://docs.chef.io/automate/ha_performance_benchmarks/#performance-benchmarks) for more info.
+See the [performance benchmarking documentation](https://docs.chef.io/automate/ha_performance_benchmarks/#performance-benchmarks) for more information.
 
 ### Cloud Deployment using Amazon Web Services (AWS)
 
@@ -113,7 +116,7 @@ The two-step deployment process is as shown below:
 The two-step deployment process is as shown below:
 
 - Provisioning Infrastructure: Manually provision the infrastructure
-- Deployment of services on the provisioned infrastructure (follow the [On-premise Deployment steps](/automate/ha_onprim_deployment_procedure/)).
+- Deployment of services on the provisioned infrastructure (follow the [on-premises deployment procedure](/automate/ha_onprim_deployment_procedure/)).
   - Installation of *PostgreSQL*, *OpenSearch*, *Chef Automate*, and *Chef Infra Server* will be done in this step.
 - Only File System Backup and Restore are supported.
 
@@ -122,7 +125,7 @@ The two-step deployment process is as shown below:
 The two-step deployment process is as shown below:
 
 - Provisioning Infrastructure: Manually provision the infrastructure
-- Deployment of services on the provisioned infrastructure (follow the [On-premise Deployment steps](/automate/ha_onprim_deployment_procedure/)).
+- Deployment of services on the provisioned infrastructure (follow the [on-premises deployment procedure](/automate/ha_onprim_deployment_procedure/)).
   - Installation of *PostgreSQL*, *OpenSearch*, *Chef Automate*, and *Chef Infra Server* will be done in this step.
 
 ## Performance (Benchmarking)

components/docs-chef-io/content/automate/ha_on_premises_deployment_prerequisites.md

@@ -92,6 +92,8 @@ Current Automate HA integrates with the following non-Chef tools:
 
 ### Minimum Hardware Requirement
 
+An eleven-node Automate HA cluster has the following minimum hardware requirements.
+
 | Instance          | Count | vCPU | RAM | Storage Size(/hab) | AWS Machine Type | AZURE Machine Type | GCP Machine Type | Additional Space      |
 | ----------------- | ----- | ---- | --- | ------------------ | ---------------- | ------------------ | ---------------- | -----------------     |
 | Chef Automate     | 2     | 2    | 8   | 200 GB             | m5.large         | Standard_D2as_v4   | n2-standard-2    | /var/tmp=5% /root=20% |
@@ -100,9 +102,7 @@ Current Automate HA integrates with the following non-Chef tools:
 | OpenSearch DB     | 3     | 2    | 8   | 200 GB             | m5.large         | Standard_D2as_v4   | n2-standard-2    | /var/tmp=5% /root=20% |
 | Bastion Machine   | 1     | 2    | 8   | 200 GB             | m5.large         | Standard_D2as_v4   | n2-standard-2    | /var/tmp=5% /root=20% |
 
-{{< note >}}
-For production, OpenSearch volume size also depends on the number of nodes and frequency of Chef Infra Client runs and compliance scans.
-{{< /note >}}
+{{< note >}} For production, OpenSearch volume size also depends on the number of nodes and frequency of Chef Infra Client runs and compliance scans. {{< /note >}}
 
 ### Load Balancer
 
@@ -155,17 +155,15 @@ Generate the certificates using recommended tools and supported algorithms and v
 - OpenSSL Algorithms: PBE-SHA1-3DES, RSA (2048), SHA-256
 - Certificate Format: X509 V3(PEM format) ,Private key is in PKCS8 format
 
-
 To understand how to generate certificates, refer to the [Certificate Generation](/automate/ha_cert_selfsign/#creating-a-certificate) documentation.
 
-
 ## Deployment Specific Pre-requisites
 
 The on-premises deployment specific pre-requisites are as follows:
 
 ### Infra Server
 
-- Chef Automate HA comes with a bundled Infra Server, and it is recommended not to use any external server in Automate HA. Using an external server will lose the Automate HA functionalities, and things may not work as expected.
+- Chef Automate HA comes with a bundled Infra Server.
 
 ### Access
 
@@ -259,7 +257,7 @@ To know more about the on-premises deployment disaster recovery, visit our [Disa
 | Existing System | Supported Setup Type | Minimum Eligible System Version | Maximum Eligible System Version |  Pre-requisite Before Migration |
 |-----------------|----------------------|---------------------------------|-----------|------------------------------|
 | Chef Automate | [Standalone](/automate/install/) | Automate 2020XXXXXX |    | To migrate to the Managed OpenSearch Automate HA cluster, the current standalone Chef Automate version should be at most 4.3.0. |
-| Chef Backend | [Chef Backend Cluster](/server/install_server_ha/) | Backend 2.X and Infra Server 14.X | Chef Infra Server 15.4.0 | Chef Backend using PostgreSQL storage for Cookbooks should only migrate to Automate HA. | 
+| Chef Backend | [Chef Backend Cluster](/server/install_server_ha/) | Backend 2.X and Infra Server 14.X | Chef Infra Server 15.4.0 | Chef Backend using PostgreSQL storage for Cookbooks should only migrate to Automate HA. |
 | Chef Infra Server | [Standalone](/server/install_server/#standalone)<br />[Tiered](/server/install_server_tiered/) | Infra server 14.XXX | Chef Infra Server 15.4.0 | Chef Infra Server using PostgreSQL storage for Cookbooks should only migrate to Automate HA. |
 | A2HA | PS Lead A2HA On-Premises Deployment |Chef Automate version 20201230192246 | Chef Automate Version 20220223121207 | The A2HA cluster-mounted backup file system should also be attached to Automate HA cluster.<br />In case of In-Place migration, the volume having `/hab` should have more than 60% free space on each node. |
 

ha_upgrade.md

@@ -19,7 +19,7 @@ This page lists the commands that aid in upgrading the Chef Automate High Availa
 - The upgrade of the backend nodes restarts ElasticSearch and PostgreSQL services.
 - You cannot downgrade the Automate version. If you intend to install the lower version of the Chef Automate High Availability (HA) system, uninstall the existing version of the same, and destroy the terraform.
 
-{{< note/ >}}
+{{< /note >}}
 
 ## Command List