Merge branch 'gh-pages-migration' into gh-pages

Bring in the docs copyedit pass (grammar, spelling, formatting fixes
across the Bare Metal deployment docs).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UkwwaPC5HaGDguqvK53i6C

Author: gm2552

docs/cloud-native-deployment.md

@@ -4,22 +4,22 @@ title: Configuration and Message Monitor Storage
 
 # Configuration and Message Monitor Storage
 
-By default, the configuration and message monitor services uses the embedded file based Derby database. Although this simplifies an out of the box solution deployment, it has several disadvantages:
+By default, the configuration and message monitor services use the embedded, file-based Derby database. Although this simplifies an out-of-the-box deployment, it has several disadvantages:
 
-* It only allows one process to access it at any one time limiting the ability to run multiple instances of the configuration service for high availability and load balancing.
+* It only allows one process to access it at any given time, limiting the ability to run multiple instances of the configuration service for high availability and load balancing.
 * Unless mounted on a network share, it is only available on the local machine.
-* It is not redundant and providers no fail over options.
+* It is not redundant and provides no failover options.
 
-These are only a small collection of issues and it becomes obvious that an enterprise/distributed database solution is needed for a robust production solution.
+These are only a small collection of issues, and it becomes obvious that an enterprise/distributed database solution is needed for a robust production deployment.
 
-The configuration and message monitoring services database configuration is held in a file named *bootstrap.properties* under the `<tomcat home>\webapps\<app name>\WEB-INF\classes` directory.  They use the standard spring datasource properties.  To connect to different database source, simply update these properties with proper database settings:
+The configuration and message monitoring services' database configuration is held in a file named *bootstrap.properties* under the `<tomcat home>\webapps\<app name>\WEB-INF\classes` directory. They use the standard Spring datasource properties. To connect to a different database source, simply update these properties with the proper database settings:
 
 * spring.datasource.url=
 * spring.datasource.username=
 * spring.datasource.password=
 
 Additional settings can be found in Spring [appendix A](https://docs.spring.io/spring-boot/docs/current/reference/html/common-application-properties.html) under the DATASOURCE section.
 
-Other database such as Oracle allow for finer grained tuning via properties; consult your database vendor for more information.
+Other databases, such as Oracle, allow for finer-grained tuning via properties; consult your database vendor for more information.
 
-After you migrate the services to your new distributed data source, it is recommended that you consider deploying multiple instance of the tomcat server using a fault tolerant and load balance configuration (instructions are beyond the scope of this document).
+After you migrate the services to your new distributed data source, it is recommended that you consider deploying multiple instances of the Tomcat server using a fault-tolerant, load-balanced configuration (instructions are beyond the scope of this document).

docs/config-store.md

@@ -4,9 +4,9 @@ title: Deployment Guide
 
 # Deployment Guide
 
-This contents in this section are a starting-point, from which a production HISP can be derived. The Bare Metal project is not intended to be a final solution for real-world scenarios. It documents the fastest and simplest way to launch an minimally operational HISP using the Java reference implementation.
+The contents of this section are a starting point from which a production HISP can be derived. The Bare Metal project is not intended to be a final solution for real-world scenarios. It documents the fastest and simplest way to launch a minimally operational HISP using the Java reference implementation.
 
-It is strongly advised and encouraged to back the reference implementation with a tested and proven enterprise mail server. Please review the various deployment models and configurations with your system architect and decide which best suits your needs. This should also involve input from you security officer to evaluate issues such as HIPAA compliance.
+It is strongly advised and encouraged to back the reference implementation with a tested and proven enterprise mail server. Please review the various deployment models and configurations with your system architect and decide which best suits your needs. This should also involve input from your security officer to evaluate issues such as HIPAA compliance.
 
 The Bare Metal install is not HIPAA compliant nor does it describe a highly available and/or fault tolerant deployment.