Cherry picked to remove old commits

doc/administration/high_availability/README.md

@@ -68,7 +68,7 @@ cost-effective to deploy several small nodes rather than a single
 larger one.
 
 - 1 PostgreSQL node
-- 1 Redis nodes
+- 1 Redis node
 - 2 or more GitLab application nodes (Unicorn, Workhorse, Sidekiq)
 - 1 NFS/Gitaly storage server
 
@@ -81,7 +81,7 @@ this architecture is required is if Sidekiq queues begin to periodically increas
 in size, indicating that there is contention or not enough resources.
 
 - 1 PostgreSQL node
-- 1 Redis nodes
+- 1 Redis node
 - 2 or more GitLab application nodes (Unicorn, Workhorse)
 - 2 or more Sidekiq nodes
 - 2 or more NFS/Gitaly storage servers

doc/administration/high_availability/nfs_host_client_setup.md

@@ -12,6 +12,9 @@ and Corosync](http://clusterlabs.org/) for highly available NFS in production.
 Below are instructions for setting up an application node(client) in an HA cluster
 to read from and write to a central NFS server(host).
 
+NOTE: **Note:**
+Using EFS may negatively impact performance. Please review the [relevant documentation](nfs.md#avoid-using-awss-elastic-file-system-efs) for additional details.
+
 ## NFS Server Setup
 
 > Follow the instructions below to set up and configure your NFS server.