Merge pull request #1087 from EnterpriseDB/content/josh/eprs-6.2-norm…

…alization Normalize Replication Server 6.2 Content Conversion
EnterpriseDB · Mar 19, 2021 · e9c71c3 · e9c71c3
2 parents 60b5d8b + 18a516b
commit e9c71c3
Show file tree

Hide file tree

Showing 325 changed files with 4,467 additions and 8,137 deletions.
diff --git a/.husky/.gitignore b/.husky/.gitignore
@@ -0,0 +1 @@
+_
diff --git a/.husky/pre-commit b/.husky/pre-commit
@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+yarn pretty-quick --staged --pattern 'src/**/*.js' --pattern 'gatsby-*.js'
diff --git a/gatsby-config.js b/gatsby-config.js
@@ -131,10 +131,6 @@ const indexQuery = `
 
 /********** Gatsby config *********/
 module.exports = {
-  flags: {
-    PRESERVE_WEBPACK_CACHE: true,
-    FAST_REFRESH: true,
-  },
   pathPrefix: '/docs',
   siteMetadata: {
     title: 'EDB Docs',

diff --git a/package.json b/package.json
@@ -14,6 +14,7 @@
     "format": "prettier --write src/**/*.js gatsby-*.js",
     "build": "gatsby build --prefix-paths",
     "serve-build": "gatsby serve --prefix-paths",
+    "prepare": "husky install",
     "update-icons": "git submodule update --init --remote && node scripts/createIconTypes.js && node scripts/createIconNames.js",
     "build-pdf": "docker-compose -f docker/docker-compose.build-pdf.yaml run --rm --entrypoint scripts/pdf/generate_pdf.py pdf-builder",
     "build-all-pdfs": "for i in product_docs/docs/**/*/ ; do echo \"$i\"; yarn build-pdf ${i%} || exit 1; done",
@@ -23,43 +24,37 @@
     "heroku-postbuild": "gatsby build",
     "build-legacy-redirects-nginx": "gatsby clean && gatsby build --prefix-paths && python3 scripts/legacy_redirects/clean_up_output.py"
   },
-  "husky": {
-    "hooks": {
-      "pre-commit": "pretty-quick --staged --pattern 'src/**/*.js' --pattern 'gatsby-*.js'"
-    }
-  },
   "dependencies": {
     "@mdx-js/mdx": "^1.6.1",
     "@mdx-js/react": "^1.6.1",
     "algoliasearch": "^4.2.0",
     "balance-text": "^3.3.0",
-    "bl": "4.0.3",
+    "bl": "4.1.0",
     "bootstrap": "4.6.0",
-    "gatsby": "^2.31.1",
-    "gatsby-cli": "^2.12.93",
-    "gatsby-image": "^2.4.1",
-    "gatsby-plugin-algolia": "^0.16.3",
-    "gatsby-plugin-catch-links": "^2.6.0",
+    "gatsby": "^3.1.0",
+    "gatsby-cli": "^3.1.0",
+    "gatsby-plugin-algolia": "^0.17.0",
+    "gatsby-plugin-catch-links": "^3.0.0",
     "gatsby-plugin-google-fonts": "^1.0.1",
-    "gatsby-plugin-google-tagmanager": "^2.10.0",
-    "gatsby-plugin-manifest": "^2.4.10",
-    "gatsby-plugin-mdx": "^1.2.6",
+    "gatsby-plugin-google-tagmanager": "^3.0.0",
+    "gatsby-plugin-manifest": "^3.0.0",
+    "gatsby-plugin-mdx": "^2.0.1",
     "gatsby-plugin-meta-redirect": "^1.1.1",
-    "gatsby-plugin-netlify": "^2.3.13",
+    "gatsby-plugin-netlify": "^3.0.1",
     "gatsby-plugin-nginx-redirect": "^0.0.11",
-    "gatsby-plugin-react-helmet": "^3.3.1",
+    "gatsby-plugin-react-helmet": "^4.0.0",
     "gatsby-plugin-react-svg": "^3.0.0",
     "gatsby-plugin-remove-fingerprints": "^0.0.2",
-    "gatsby-plugin-sass": "^3.1.0",
-    "gatsby-plugin-sharp": "^2.13.2",
-    "gatsby-plugin-sitemap": "^2.4.13",
-    "gatsby-remark-autolink-headers": "^2.3.1",
-    "gatsby-remark-images": "^3.10.0",
-    "gatsby-remark-prismjs": "^3.5.4",
-    "gatsby-source-filesystem": "^2.3.1",
-    "gatsby-transformer-json": "^2.4.3",
-    "gatsby-transformer-remark": "^2.8.15",
-    "gatsby-transformer-sharp": "^2.5.1",
+    "gatsby-plugin-sass": "^4.0.2",
+    "gatsby-plugin-sharp": "^3.0.1",
+    "gatsby-plugin-sitemap": "^3.0.0",
+    "gatsby-remark-autolink-headers": "^3.0.0",
+    "gatsby-remark-images": "4.0.0",
+    "gatsby-remark-prismjs": "^4.0.0",
+    "gatsby-source-filesystem": "^3.0.0",
+    "gatsby-transformer-json": "^3.0.0",
+    "gatsby-transformer-remark": "^3.0.0",
+    "gatsby-transformer-sharp": "^3.0.0",
     "graceful-fs": "^4.2.4",
     "is-absolute-url": "^3.0.3",
     "markdown-to-jsx": "^7.0.0",
@@ -77,7 +72,7 @@
     "fast-glob": "^3.2.5",
     "hast-util-is-element": "^1.1.0",
     "hast-util-to-text": "^2.0.1",
-    "husky": "^4.3.5",
+    "husky": "^5.1.3",
     "prettier": "^2.2.1",
     "pretty-quick": "^3.1.0",
     "react-refresh": "^0.9.0",
@@ -88,6 +83,7 @@
     "remark-frontmatter": "^2.0.0",
     "remark-mdx": "^1.6.22",
     "remark-stringify": "^8.1.1",
+    "semver-compare": "^1.0.0",
     "to-vfile": "^6.1.0",
     "typescript": "^4.1.3"
   },

diff --git a/product_docs/docs/ark/3.5/ark_v3.5_documentation.pdf b/product_docs/docs/ark/3.5/ark_v3.5_documentation.pdf
diff --git a/product_docs/docs/bart/2.4/bart_v2.4_documentation.pdf b/product_docs/docs/bart/2.4/bart_v2.4_documentation.pdf
diff --git a/product_docs/docs/bart/2.5.1/bart_v2.5.1_documentation.pdf b/product_docs/docs/bart/2.5.1/bart_v2.5.1_documentation.pdf
diff --git a/product_docs/docs/bart/2.5.2/bart_v2.5.2_documentation.pdf b/product_docs/docs/bart/2.5.2/bart_v2.5.2_documentation.pdf
diff --git a/product_docs/docs/bart/2.5.3/bart_v2.5.3_documentation.pdf b/product_docs/docs/bart/2.5.3/bart_v2.5.3_documentation.pdf
diff --git a/product_docs/docs/bart/2.5.4/bart_v2.5.4_documentation.pdf b/product_docs/docs/bart/2.5.4/bart_v2.5.4_documentation.pdf
diff --git a/product_docs/docs/bart/2.5.5/bart_v2.5.5_documentation.pdf b/product_docs/docs/bart/2.5.5/bart_v2.5.5_documentation.pdf
diff --git a/product_docs/docs/bart/2.5.7/bart_v2.5.7_documentation.pdf b/product_docs/docs/bart/2.5.7/bart_v2.5.7_documentation.pdf
diff --git a/product_docs/docs/bart/2.6.1/bart_v2.6.1_documentation.pdf b/product_docs/docs/bart/2.6.1/bart_v2.6.1_documentation.pdf
diff --git a/product_docs/docs/bart/2.6/bart_v2.6_documentation.pdf b/product_docs/docs/bart/2.6/bart_v2.6_documentation.pdf
diff --git a/product_docs/docs/efm/3.10/efm_v3.10_documentation.pdf b/product_docs/docs/efm/3.10/efm_v3.10_documentation.pdf
diff --git a/product_docs/docs/efm/3.5/efm_v3.5_documentation.pdf b/product_docs/docs/efm/3.5/efm_v3.5_documentation.pdf
diff --git a/product_docs/docs/efm/3.6/efm_v3.6_documentation.pdf b/product_docs/docs/efm/3.6/efm_v3.6_documentation.pdf
diff --git a/product_docs/docs/efm/3.7/efm_v3.7_documentation.pdf b/product_docs/docs/efm/3.7/efm_v3.7_documentation.pdf
diff --git a/product_docs/docs/efm/3.8/efm_v3.8_documentation.pdf b/product_docs/docs/efm/3.8/efm_v3.8_documentation.pdf
diff --git a/product_docs/docs/efm/3.9/efm_v3.9_documentation.pdf b/product_docs/docs/efm/3.9/efm_v3.9_documentation.pdf
diff --git a/product_docs/docs/efm/4.0/efm_v4.0_documentation.pdf b/product_docs/docs/efm/4.0/efm_v4.0_documentation.pdf
diff --git a/product_docs/docs/efm/4.1/efm_v4.1_documentation.pdf b/product_docs/docs/efm/4.1/efm_v4.1_documentation.pdf
diff --git a/product_docs/docs/epas/10/epas_v10_documentation.pdf b/product_docs/docs/epas/10/epas_v10_documentation.pdf
diff --git a/product_docs/docs/epas/11/epas_v11_documentation.pdf b/product_docs/docs/epas/11/epas_v11_documentation.pdf
diff --git a/product_docs/docs/epas/12/epas_v12_documentation.pdf b/product_docs/docs/epas/12/epas_v12_documentation.pdf
diff --git a/product_docs/docs/epas/13/epas_v13_documentation.pdf b/product_docs/docs/epas/13/epas_v13_documentation.pdf
diff --git a/product_docs/docs/epas/9.5/epas_v9.5_documentation.pdf b/product_docs/docs/epas/9.5/epas_v9.5_documentation.pdf
diff --git a/product_docs/docs/epas/9.6/epas_v9.6_documentation.pdf b/product_docs/docs/epas/9.6/epas_v9.6_documentation.pdf
diff --git a/product_docs/docs/eprs/6.2/01_introduction/01_whats_new.mdx b/product_docs/docs/eprs/6.2/01_introduction/01_whats_new.mdx
@@ -4,10 +4,9 @@ title: "What’s New"
 
 <div id="whats_new" class="registered_link"></div>
 
-
 The following features have been added to xDB Replication Server version 6.1 to create xDB Replication Server version 6.2:
 
 > -   Registering your xDB Replication Server product with an EnterpriseDB product license key is no longer required. Thus, all components related to registering the product have been removed. The following are the removed components: 1) the Product Registration dialog box accessed from the xDB Replication Console Help menu, 2) the `license_key` parameter located in the xDB Replication Configuration file, and 3) the xDB Replication Server CLI `registerkey` command.
-> -   Partitioned tables created using the declarative partitioning feature of PostgreSQL and Advanced Server version 10 and later can now be replicated in a log-based single-master or multi-master replication system. For more information, see [Replicating Postgres Partitioned Tables](../07_common_operations/#replicating_postgres_partitioned_tables).
-> -   In a single-master replication system, removal of a table from a publication that has one or more existing subscriptions is now permitted as long as the table to be removed is not the parent referenced in a foreign key constraint from a child table that is not being removed as well. Previously, no tables from a publication in a single-master replication system could be removed if there are existing subscriptions. For more information, see [Removing Tables from a Publication](../07_common_operations/06_managing_publication/#remove_tables_from_pub).
+> -   Partitioned tables created using the declarative partitioning feature of PostgreSQL and Advanced Server version 10 and later can now be replicated in a log-based single-master or multi-master replication system. For more information, see [Replicating Postgres Partitioned Tables](../07_common_operations/10_replicating_postgres_partitioned_tables/#replicating_postgres_partitioned_tables).
+> -   In a single-master replication system, removal of a table from a publication that has one or more existing subscriptions is now permitted as long as the table to be removed is not the parent referenced in a foreign key constraint from a child table that is not being removed as well. Previously, no tables from a publication in a single-master replication system could be removed if there are existing subscriptions. For more information, see [Removing Tables from a Publication](../07_common_operations/06_managing_publication/03_updating_pub/#remove_tables_from_pub).
 > -   Versions 11 and 12 of PostgreSQL and Advanced Server are now supported.
diff --git a/product_docs/docs/eprs/6.2/01_introduction/02_conventions_used.mdx b/product_docs/docs/eprs/6.2/01_introduction/02_conventions_used.mdx
@@ -4,7 +4,6 @@ title: "Conventions Used in this Guide"
 
 <div id="conventions_used" class="registered_link"></div>
 
-
 The following is a list of other conventions used throughout this document.
 
 -   This guide applies to both Linux and Windows systems. Directory paths are presented in the Linux format with forward slashes. When working on Windows systems, start the directory path with the drive letter followed by a colon and substitute back slashes for forward slashes.

diff --git a/product_docs/docs/eprs/6.2/01_introduction/03_certified_supported_versions.mdx b/product_docs/docs/eprs/6.2/01_introduction/03_certified_supported_versions.mdx
@@ -2,8 +2,6 @@
 title: "Certified and Supported Product Versions"
 ---
 
-
-
 The following database product versions may be used with xDB Replication Server:
 
 -   PostgreSQL versions 9.6, 10, 11, 12, and 13
@@ -15,7 +13,7 @@ The following database product versions may be used with xDB Replication Server:
 -   SQL Server 2012 version 11.0.6020.0 has been explicitly certified. Newer minor versions in the 11.0 line are supported as well.
 -   SQL Server 2014 version 12.0.5000.0 has been explicitly certified. Newer minor versions in the 12.0 line are supported as well.
 
-Contact your EnterpriseDB Account Manager or <[email protected]> if you require support for other platforms.
+Contact your EnterpriseDB Account Manager or [[email protected]](mailto:[email protected]) if you require support for other platforms.
 
 **A Note Regarding Oracle RAC and Oracle Exadata**
 

diff --git a/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx
@@ -2,22 +2,17 @@
 title: "Supported JDK Versions"
 ---
 
-
-
 The xDB Replication Server is certified to work with the following Java platforms:
 
-<table style="width:14%;"><caption><strong>Certified Java Platforms</strong></caption><colgroup><col style="width: 5%" /><col style="width: 8%" /></colgroup><thead><tr class="header"><th><strong>Operating Systems</strong></th><th><strong>JDK Versions</strong></th></tr></thead><tbody><tr class="odd"><td><p><code>CentOS 7 and 8</code></p></td><td><ul><li>Red Hat OpenJDK 7</li><li>Red Hat OpenJDK 8</li></ul></td></tr><tr class="even"><td><code>PPCLE RHEL7</code></td><td><blockquote><p>Red Hat OpenJDK 8</p></blockquote></td></tr><tr class="odd"><td><p><code>RHEL 7</code></p></td><td><ul><li>Red Hat OpenJDK 7</li><li>Red Hat OpenJDK 8</li><li>Oracle JDK 7</li><li>Oracle JDK 8</li></ul></td></tr><tr class="even"><td><p><code>Windows 2012 R2, 2016, and 2019</code></p></td><td><ul><li>Red Hat OpenJDK 7</li><li>Red Hat OpenJDK 8</li></ul></td></tr><tr class="odd"><td><code>Debian 10</code></td><td><blockquote><p>Red Hat OpenJDK 11</p></blockquote></td></tr></tbody></table>
+| **Operating Systems**                   | **JDK Versions**                                                                                                          |
+| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| `CentOS 7 and 8`<br />                  | -   Red Hat OpenJDK 7     <br /> -   Red Hat OpenJDK 8     <br />                                                         |
+| `PPCLE RHEL7`                           | <br /><br /><br />Red Hat OpenJDK 8<br /><br />                                                                           |
+| `RHEL 7`<br />                          | -   Red Hat OpenJDK 7     <br /> -   Red Hat OpenJDK 8     <br /> -   Oracle JDK 7     <br /> -   Oracle JDK 8     <br /> |
+| `Windows 2012 R2, 2016, and 2019`<br /> | -   Red Hat OpenJDK 7     <br /> -   Red Hat OpenJDK 8     <br />                                                         |
+| `Debian 10`                             | <br /><br /><br />Red Hat OpenJDK 11<br /><br />                                                                          |
 
 **Certified Java Platforms**
 
-<div class="note">
-
-<div class="title">
-
-Note
-
-</div>
-
-EDB Postgres Replication Server 6.2 is no longer supported on `CentOS/RHEL/OEL 6.x` platforms. It is strongly recommended that EDB products running on these platforms should be migrated to a supported platform.
-
-</div>
+!!! Note
+    EDB Postgres Replication Server 6.2 is no longer supported on `CentOS/RHEL/OEL 6.x` platforms. It is strongly recommended that EDB products running on these platforms should be migrated to a supported platform.
diff --git a/product_docs/docs/eprs/6.2/01_introduction/index.mdx b/product_docs/docs/eprs/6.2/01_introduction/index.mdx
@@ -4,7 +4,6 @@ title: "Introduction"
 
 <div id="introduction" class="registered_link"></div>
 
-
 This document describes the installation, configuration, architecture, and operation of the <span class="title-ref">EDB xDB Replication Server</span>. EDB xDB (cross database) Replication Server (referred to hereafter as <span class="title-ref">xDB Replication Server</span>) is an asynchronous replication system available for PostgreSQL and for EDB Postgres Advanced Server. The latter will be referred to simply as <span class="title-ref">Advanced Server</span>.
 
 xDB Replication Server can be used to implement replication systems based on either of two different replication models – single-master (primary-to-secondary) replication or multi-master replication.
@@ -26,17 +25,8 @@ The following are some combinations of cross database replications that xDB Repl
 -   From PostgreSQL to Oracle (WAL mode)
 -   From PostgreSQL to Oracle (trigger mode)
 
-<div class="note">
-
-<div class="title">
-
-Note
-
-</div>
-
-Oracle Real Application Clusters (RAC) and Oracle Exadata are not supported by xDB Replication Server. These Oracle products have not been evaluated nor certified with xDB Replication Server.
-
-</div>
+!!! Note
+    Oracle Real Application Clusters (RAC) and Oracle Exadata are not supported by xDB Replication Server. These Oracle products have not been evaluated nor certified with xDB Replication Server.
 
 For multi-master replication, xDB Replication Server supports the following configurations:
 
@@ -46,18 +36,18 @@ For multi-master replication, xDB Replication Server supports the following conf
 The reader is assumed to have basic SQL knowledge and basic Oracle, SQL Server, or PostgreSQL database administration skills (whichever are applicable) so that databases, users, schemas, and tables can be created and database object privileges assigned.
 
 -   The remainder of Chapter 1 describes conventions used throughout this user’s guide along with suggested sections to read based upon your purpose for using this guide.
--   Chapter [Overview](02_overview/#overview) provides an overview of xDB Replication Server including basic replication concepts and definitions, architecture and components of xDB Replication Server, and design guidelines for setting up a replication system.
--   Chapter [Installation and Uninstallation](03_installation/#installation) gives instructions for installing and uninstalling xDB Replication Server.
--   Chapter [Introduction to the xDB Replication Console](#intro_xdb_console) provides an overview of the xDB Replication Console, the graphical user interface for using xDB Replication Server.
--   Chapter [Single-Master Replication Operation](05_smr_operation/#smr_operation) gives instructions for the configuration and operation of xDB Replication Server for single-master replication systems.
--   Chapter [Multi-Master Replication Operation](06_mmr_operation/#mmr_operation) gives instructions for the configuration and operation of xDB Replication Server for multi-master replication systems.
--   Chapter [Common Operations](07_common_operations/#common_operations) describes operations that are common to both single-master and multi-master replication systems.
--   Chapter [xDB Replication Server Command Line Interface](08_xdb_cli/#xdb_cli) describes the xDB Replication Server Command Line Interface, an alternative to the graphical user interface for xDB Replication Server configuration and management.
--   Chapter [Data Validator](09_data_validator/#data_validator) gives instructions for configuration and usage of the Data Validator.
--   Chapter [Appendix](10_appendix/#appendix) is an appendix containing troubleshooting tips, a list of error messages, their causes and resolutions, permitted combinations of database servers in a replication system, xDB Replication Server product upgrade procedures, and other miscellaneous technical information.
+-   Chapter [Overview](../02_overview/#overview) provides an overview of xDB Replication Server including basic replication concepts and definitions, architecture and components of xDB Replication Server, and design guidelines for setting up a replication system.
+-   Chapter [Installation and Uninstallation](../03_installation/#installation) gives instructions for installing and uninstalling xDB Replication Server.
+-   Chapter [Introduction to the xDB Replication Console](../04_intro_xdb_console/#intro_xdb_console) provides an overview of the xDB Replication Console, the graphical user interface for using xDB Replication Server.
+-   Chapter [Single-Master Replication Operation](../05_smr_operation/#smr_operation) gives instructions for the configuration and operation of xDB Replication Server for single-master replication systems.
+-   Chapter [Multi-Master Replication Operation](../06_mmr_operation/#mmr_operation) gives instructions for the configuration and operation of xDB Replication Server for multi-master replication systems.
+-   Chapter [Common Operations](../07_common_operations/#common_operations) describes operations that are common to both single-master and multi-master replication systems.
+-   Chapter [xDB Replication Server Command Line Interface](../08_xdb_cli/#xdb_cli) describes the xDB Replication Server Command Line Interface, an alternative to the graphical user interface for xDB Replication Server configuration and management.
+-   Chapter [Data Validator](../09_data_validator/#data_validator) gives instructions for configuration and usage of the Data Validator.
+-   Chapter [Appendix](../10_appendix/#appendix) is an appendix containing troubleshooting tips, a list of error messages, their causes and resolutions, permitted combinations of database servers in a replication system, xDB Replication Server product upgrade procedures, and other miscellaneous technical information.
 
 <div class="toctree" maxdepth="3">
 
-whats\_new conventions\_used certified\_supported\_versions supported\_jdk\_versions
+whats_new conventions_used certified_supported_versions supported_jdk_versions
 
 </div>
diff --git a/...s/6.2/02_overview/01_why_replication/01_offloading_reporting_and_bi_queries.mdx b/...s/6.2/02_overview/01_why_replication/01_offloading_reporting_and_bi_queries.mdx
@@ -4,7 +4,6 @@ title: "Offloading Reporting and Business Intelligence Queries"
 
 <div id="offloading_reporting_and_bi_queries" class="registered_link"></div>
 
-
 In this use case, users take all or just a subset of data from a production OLTP system and replicate it to another database whose sole purpose is to support reporting queries. This can have multiple benefits:
 
 1.  Reporting loads are removed from the OLTP system, improving transaction processing performance.

diff --git a/...uct_docs/docs/eprs/6.2/02_overview/01_why_replication/02_using_warm_standby.mdx b/...uct_docs/docs/eprs/6.2/02_overview/01_why_replication/02_using_warm_standby.mdx
@@ -4,5 +4,4 @@ title: "Using Warm Standby Servers"
 
 <div id="using_warm_standby" class="registered_link"></div>
 
-
 When many organizations wish to improve the availability of their data, a cost effective solution is often the use of warm standby servers. These are database servers kept up to date with the online system through replication that can be brought online quickly in the event of a failure in the production system. Warm standby servers can also be used for regular maintenance by gracefully switching over to the standby server so that the production server can be brought offline for regular maintenance.
diff --git a/...docs/eprs/6.2/02_overview/01_why_replication/03_testing_systems_in_parallel.mdx b/...docs/eprs/6.2/02_overview/01_why_replication/03_testing_systems_in_parallel.mdx
@@ -4,5 +4,4 @@ title: "Testing Systems in Parallel"
 
 <div id="testing_systems_in_parallel" class="registered_link"></div>
 
-
 Often times, upgrading or moving to a new database system requires that the old and new systems be up and running in parallel to allow for testing and comparing results in real time. Replication can be employed in this use case and is frequently used in development and testing environments.
diff --git a/product_docs/docs/eprs/6.2/02_overview/01_why_replication/04_migrating_data.mdx b/product_docs/docs/eprs/6.2/02_overview/01_why_replication/04_migrating_data.mdx
@@ -4,7 +4,6 @@ title: "Migrating Data"
 
 <div id="migrating_data" class="registered_link"></div>
 
-
 Similar to running in parallel, is the situation where data may be migrated from one system to another in a sort of *seeding* operation. Replication can be very effective in this situation by quickly copying data.
 
 Some reasons to consider multi-master replication include the following:
diff --git a/...uct_docs/docs/eprs/6.2/02_overview/01_why_replication/05_write_availability.mdx b/...uct_docs/docs/eprs/6.2/02_overview/01_why_replication/05_write_availability.mdx
@@ -4,5 +4,4 @@ title: "Write Availability"
 
 <div id="write_availability" class="registered_link"></div>
 
-
 In single-master replication, only the primary database is available for writes. The secondary databases are read-only for applications. If the replicated target databases must be available for write access as well, multi-master replication can be employed for the same use cases as outlined for single-master replication, but with the additional advantage of write access to the secondary.
diff --git a/product_docs/docs/eprs/6.2/02_overview/01_why_replication/06_write_scalability.mdx b/product_docs/docs/eprs/6.2/02_overview/01_why_replication/06_write_scalability.mdx
@@ -4,5 +4,4 @@ title: "Write Scalability"
 
 <div id="write_scalability" class="registered_link"></div>
 
-
 In write-intensive applications, multi-master replication allows you to utilize multiple database servers on separate hosts to process write transactions independently of each other on their own primary databases. Changes can then be reconciled across primary databases according to your chosen schedule.
diff --git a/..._docs/docs/eprs/6.2/02_overview/01_why_replication/07_localized_data_access.mdx b/..._docs/docs/eprs/6.2/02_overview/01_why_replication/07_localized_data_access.mdx
@@ -4,5 +4,4 @@ title: "Localized Data Access"
 
 <div id="localized_data_access" class="registered_link"></div>
 
-
 In a geographically dispersed application, local access to the database can be provided to regions of clients. Having the database servers physically close to clients can reduce latency with the database. Multi-master replication allows you to employ a WAN connected network of primary databases that can be geographically close to groups of clients, yet maintain data consistency across primary databases.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,7 +4,6 @@ title: "Conventions Used in this Guide"

		<div id="conventions_used" class="registered_link"></div>


		The following is a list of other conventions used throughout this document.

		- This guide applies to both Linux and Windows systems. Directory paths are presented in the Linux format with forward slashes. When working on Windows systems, start the directory path with the drive letter followed by a colon and substitute back slashes for forward slashes.
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,7 +4,6 @@ title: "Offloading Reporting and Business Intelligence Queries"

		<div id="offloading_reporting_and_bi_queries" class="registered_link"></div>


		In this use case, users take all or just a subset of data from a production OLTP system and replicate it to another database whose sole purpose is to support reporting queries. This can have multiple benefits:

		1. Reporting loads are removed from the OLTP system, improving transaction processing performance.
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,5 +4,4 @@ title: "Using Warm Standby Servers"

		<div id="using_warm_standby" class="registered_link"></div>


		When many organizations wish to improve the availability of their data, a cost effective solution is often the use of warm standby servers. These are database servers kept up to date with the online system through replication that can be brought online quickly in the event of a failure in the production system. Warm standby servers can also be used for regular maintenance by gracefully switching over to the standby server so that the production server can be brought offline for regular maintenance.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,5 +4,4 @@ title: "Testing Systems in Parallel"

		<div id="testing_systems_in_parallel" class="registered_link"></div>


		Often times, upgrading or moving to a new database system requires that the old and new systems be up and running in parallel to allow for testing and comparing results in real time. Replication can be employed in this use case and is frequently used in development and testing environments.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,7 +4,6 @@ title: "Migrating Data"

		<div id="migrating_data" class="registered_link"></div>


		Similar to running in parallel, is the situation where data may be migrated from one system to another in a sort of seeding operation. Replication can be very effective in this situation by quickly copying data.

		Some reasons to consider multi-master replication include the following:
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,5 +4,4 @@ title: "Write Availability"

		<div id="write_availability" class="registered_link"></div>


		In single-master replication, only the primary database is available for writes. The secondary databases are read-only for applications. If the replicated target databases must be available for write access as well, multi-master replication can be employed for the same use cases as outlined for single-master replication, but with the additional advantage of write access to the secondary.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,5 +4,4 @@ title: "Write Scalability"

		<div id="write_scalability" class="registered_link"></div>


		In write-intensive applications, multi-master replication allows you to utilize multiple database servers on separate hosts to process write transactions independently of each other on their own primary databases. Changes can then be reconciled across primary databases according to your chosen schedule.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,5 +4,4 @@ title: "Localized Data Access"

		<div id="localized_data_access" class="registered_link"></div>


		In a geographically dispersed application, local access to the database can be provided to regions of clients. Having the database servers physically close to clients can reduce latency with the database. Multi-master replication allows you to employ a WAN connected network of primary databases that can be geographically close to groups of clients, yet maintain data consistency across primary databases.