Documentation fixes and improvements

README.md

@@ -5,25 +5,25 @@
 [![Documentation](https://img.shields.io/badge/docs-view-green.svg)](https://documentation.wazuh.com)
 [![Web](https://img.shields.io/badge/web-view-green.svg)](https://wazuh.com)
 
-This repository includes the template and scripts for setting up both demo and production ready environments:
+This repository contains CloudFormation templates and provision scripts to deploy both a Wazuh production-ready environment and a Wazuh demo environment in Amazon Web Services (AWS):
 
-## Demo environment:
+## Production-ready environment:
 
 * A VPC with two subnets, one for Wazuh servers, and another for Elastic Stack
 * Wazuh managers cluster with two nodes, a master and a worker
 * An Elasticsearch cluster with a minimum of 3 data nodes, auto-scalable to a maximum of 6 nodes
 * A Kibana node that includes a local elasticsearch client node, and an Nginx for HTTP basic authentication
 * Wazuh servers seat behind an internet-facing load balancer for agents to communicate with the cluster
 * Kibana server seats behind an internet facing load balancer, that optionally loads an SSL Certificate for HTTPS
-* A Splunk Indexer instance with a Splunk app for Wazuh installed on it.
-* Six Wazuh agents installed on different operating systems: Red Hat 7, CentOS 7, Ubuntu, Debian, Amazon Linux and Windows.
+* Route53 DNS records for the loadbalancer, Wazuh and Elastic Stack nodes (optional).
 
-## Production-ready environment:
+## Demo environment:
 
 * A VPC with two subnets, one for Wazuh servers, and another for Elastic Stack
 * Wazuh managers cluster with two nodes, a master and a worker
 * An Elasticsearch cluster with a minimum of 3 data nodes, auto-scalable to a maximum of 6 nodes
 * A Kibana node that includes a local elasticsearch client node, and an Nginx for HTTP basic authentication
 * Wazuh servers seat behind an internet-facing load balancer for agents to communicate with the cluster
 * Kibana server seats behind an internet facing load balancer, that optionally loads an SSL Certificate for HTTPS
-* Route53 DNS records for the loadbalancer, Wazuh and Elastic Stack nodes (optional).
+* A Splunk Indexer instance with a Splunk app for Wazuh installed on it.
+* Six Wazuh agents installed on different operating systems: Red Hat 7, CentOS 7, Ubuntu, Debian, Amazon Linux and Windows.

production/README.md

@@ -81,12 +81,12 @@ Once registered, new agents can connect to the Wazuh cluster, via TCP, using the
 
 ## Optional DNS records
 
-`EnableDNSRecord`, `Subdomain` and `HostedZoneName` parameters configure the DNS records.
+Optionally it is possible to deploy DNS records for the loadbalancer, Wazuh nodes and Elastic Stack nodes. The `EnableDNSRecord`, `Subdomain` and `HostedZoneName` parameters configure the related Route 53 settings.
 
-- The DNS records can be enable/disable throught the `EnableDNSRecord` parameter.
-- The `Subdomain` parameter sets the subdomain name for the loadbalancer.
-- `HostedZoneName` sets the parent domain for the loadbalancer and the instances.
-- The subdomain name is fixed for the Elastic Stack and Wazuh nodes.
+* `EnableDNSRecord` parameter enables/disables the DNS record usage.
+* `HostedZoneName` sets the parent domain for the loadbalancer and the instances.
+* The `Subdomain` parameter sets the subdomain name for the loadbalancer.
+* Elastic Stack nodes and Wazuh nodes subdomain names are hardcoded on the CloudFormation template.
 
 
 ## Parameters template
@@ -173,6 +173,6 @@ The following template contains an example list of parameters and value placehol
 ]
 ```
 
-## AWS demo environment diagram
+## AWS production environment diagram
 
 ![wazuh_template](images/wazuh_template-designer.png)