EnterpriseDB · nidhibhammar · Oct 16, 2023 · Oct 12, 2023 · Oct 16, 2023
@@ -11,10 +11,10 @@ On Windows systems, the publication server and subscription server run as servic
 
 ## Linux details
 
-On Linux hosts where you installed Replication Server with the graphical user interface or from the command line, you should now have a publication server daemon and a subscription server daemon running on your computer, assuming you chose to install the publication server and subscription server components. If you installed the Replication Server RPM package, you must start the publication server and the subscription server based on the instructions in [Registering a Publication Server](../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) for the publication server and [Registering a Subscription Server](../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for the subscription server.
+On Linux hosts where you installed Replication Server with the graphical installer or from the command line, a publication server daemon and a subscription server daemon are now running on your computer, assuming you chose to install the publication server and subscription server components. If you installed the Replication Server RPM package, you must start the publication server and the subscription server based on the instructions in [Registering a publication server](../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) for the publication server and [Registering a subscription server](../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for the subscription server.
 
 !!! Note
-    On some Linux systems, you may have to restart the server before you can see the EPRS Replication Console choice in the application menu. If the Replication Console choice is still unavailable in the application menu, it can be started by invoking the script `XDB_HOME/bin/runRepConsole.sh`.
+    On some Linux systems, you might have to restart the server before you can see the EPRS Replication Console choice in the application menu. If the Replication Console choice is still unavailable in the application menu, you can start it by invoking the script `XDB_HOME/bin/runRepConsole.sh`.
 
 ## Additional details
 
@@ -23,7 +23,7 @@ The Postgres application menu contains a new item for the EPRS Replication Conso
 !!! Note
     If Replication Server is installed from a Replication Server RPM package, start the EPRS Replication Console by invoking the script `XDB_HOME/bin/runRepConsole.sh`.
 
-During the configuration process, you may need the following files that are created during installation.
+During the configuration process, you might need the following files that are created during installation.
 
 | File Name                          | Location                              | Description                                                                          |
 | ---------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------ |
@@ -50,10 +50,10 @@ During the configuration process, you may need the following files that are crea
     - For Windows, Replication Server is installed in the `C:\Program Files\edb\EnterpriseDB-xDBReplicationServer` directory.
 
 !!! Note
-    `POSTGRES_HOME` is the home directory of the postgres operating system account (enterprisedb for Advanced Server installed in Oracle compatible configuration mode).
+    `POSTGRES_HOME` is the home directory of the postgres operating system account (enterprisedb for EDB Postgres Advanced Server installed in Oracle-compatible configuration mode).
 
 !!! Note
-    The publication and subscription services startup log files (`edb-xdbpubserver.log` and `edb-xdbsubserver.log`) are not generated for Windows and Mac OS X operating systems.
+    The publication and subscription services startup log files (`edb-xdbpubserver.log` and `edb-xdbsubserver.log`) aren't generated for Windows and Mac OS X operating systems.
 
 !!! Note
     `USER_HOME` is the home directory of the operating system account in use.

@@ -4,7 +4,7 @@ title: "Installing a JDBC driver"
 
 ## Choosing and installing a JDBC driver
 
-Which JDBC driver you use depends on what database you're using. If you're using:
+The JDBC driver you use depends on the database you're using. If you're using:
 
 - **EDB Postgres Advanced Server**, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/).
 
@@ -15,14 +15,14 @@ Which JDBC driver you use depends on what database you're using. If you're using
 - **Microsoft SQL Server**, use the freely available [Microsoft SQL Server JDBC](https://learn.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16#102) driver.
 
 !!! Note
-For Microsoft SQL Server, if your system uses JDK/JAVA then it is recommended that you use an equal or earlier mssql-jdbc jre version than the JDK/JAVA version on your system. For example, a system with JDK/JAVA version 18 can use `mssql-jdbc-11.2.0.jre18.jar`, `mssql-jdbc-11.2.0.jre17.jar`, and so on.
+For Microsoft SQL Server, if your system uses JDK/JAVA, then we recommend that you use an equal or earlier mssql-jdbc jre version than the JDK/JAVA version on your system. For example, a system with JDK/JAVA version 18 can use `mssql-jdbc-11.2.0.jre18.jar`, `mssql-jdbc-11.2.0.jre17.jar`, and so on.
 !!!
 
 ## Configuring the driver
 
 After downloading the driver, create a symlink in the `XDB-install-folder/lib/jdbc` directory that points to the location where you installed the driver. 
 
-For Linux, create a symlink for the driver using these naming conventions:
+For Linux, create a symlink for the driver using these naming conventions.
 
    |        Driver        |  symlink name  |
    | -------------------- | -------------- |
@@ -32,5 +32,4 @@ For Linux, create a symlink for the driver using these naming conventions:
    | Microsoft SQL Server | mssql-jdbc.jar |
    | jTDS                 | jtds.jar       |
 
- For Windows, the drivers need to be copied to the `XDB-install-folder/lib/jdbc` directory and renamed using the same naming conventions.
-
+ For Windows, copy the drivers to the `XDB-install-folder/lib/jdbc` directory and rename them using the same naming conventions.
@@ -7,7 +7,15 @@ redirects:
 
 <div id="uninstalling_xdb_replication_server" class="registered_link"></div>
 
-Uninstalling Replication Server results in the removal of the publication server, the subscription server, the EPRS console, the Replication Server command line interface, the EPRS replication configuration file, the Replication Server startup configuration file, the publication server configuration file, and the subscription server configuration file.
+Uninstalling Replication Server results in the removal of the fllowing:
+- Publication server
+- Subscription server
+- EPRS console
+- Replication Server command line interface
+- EPRS replication configuration file
+- Replication Server startup configuration file
+- Publication server configuration file
+- Subscription server configuration file
 
 Uninstalling Replication Server doesn't remove any databases used as primary nodes, publication databases, or subscription databases.
 
@@ -17,7 +25,7 @@ If you installed Replication Server using the Replication Server installer progr
 
 <div id="uninstalling_xdb_rpm_package" class="registered_link"></div>
 
-## Uninstalling a RPM package installation
+## Uninstalling an RPM package installation
 
 If you installed Replication Server from the RPM package, uninstall it using the yum package manager. 
 
@@ -93,23 +101,16 @@ Complete!
 
 ## Uninstalling a Windows installation
 
-The following steps are for uninstalling Replication Server from a Windows host.
+To uninstall Replication Server from a Windows host:
 
 1. From the Windows Control Panel, select **Uninstall a Program**.
 
-   ![Uninstall a program](../images/image53.png)
-
-1. Select the Replication Server product in the list of programs to uninstall or change. Select **Uninstall/Change**.
-
-   ![Uninstall or change a program](../images/image54.png)
+1. From the list of programs to uninstall or change, select the Replication Server product. Select **Uninstall/Change**.
 
 1. Select **Yes** to confirm that you want to unistall Replication Server.
 
-   ![Confirm Replication Server uninstallation](../images/image55.png)
-
-1. The Uninstallation Completed dialog box appears when the process has completed. Select **OK**.
+1. The Uninstallation Completed dialog box appears when the process is complete. Select **OK**.
 
-   ![Uninstallation completed](../images/image56.png)
 
 ### Uninstalling in text or unattended mode
 

@@ -10,11 +10,11 @@ If you have an existing Replication Server 7.x installation on Linux, you can us
 
 `yum upgrade edb-repo`
 
-`yum` will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum to upgrade any installed packages:
+`yum` updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum to upgrade any installed packages:
 
 `yum upgrade edb-xdb*`
 
-If you are upgrading from a Replication Server 6.2 installation on Linux, see [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) for details.
+If you're upgrading from a Replication Server 6.2 installation on Linux, see [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) for details.
 
 After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](../installing_jdbc_driver/) for more information.
 
@@ -1,47 +1,47 @@
 ---
-title: "Upgrading with the graphical user interface installer"
+title: "Upgrading with the graphical installer"
 redirects:
 - /eprs/7/10_appendix/02_upgrading_to_xdb6_2/02_upgrading_with_gui_installer/
 - /eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer/
 ---
 
 <div id="upgrading_with_gui_installer" class="registered_link"></div>
 
-You can upgrade to Replication Server 7 using the graphical user interface installer.
+You can upgrade to Replication Server 7 using the graphical installer.
 
 1.  Before starting the upgrade process, replicate any pending backlog of transactions on the publication tables.
 
 1.  After all pending transactions are replicated to their target databases, stop the Replication Server 6.2.x publication server and subscription server. See [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server).
 
-1. Ensure the installation user has administrative permissions on the `XDB_HOME/xdata` folder. On Windows, this can be done by opening the Replication Server installation directory in Windows Explorer and selecting the xdata folder. When prompted, select **Continue** to enable the required permission.
+1. Ensure the installation user has administrative permissions on the `XDB_HOME/xdata` folder. On Windows, you can do this by opening the Replication Server installation directory in Windows Explorer and selecting the xdata folder. When prompted, select **Continue** to enable the required permission.
 
 1.  Install Replication Server 7. See [Installation and uninstallation](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for instructions on installing Replication Server, but note the differences described in the following steps.
 
-1.  Following the acceptance of the license agreement, the Select Components screen appears but with the entries grayed out. The old Replication Server components are replaced with the new ones in the old Replication Server’s directory location. Select **Next**.
+1.  Following the acceptance of the license agreement, the Select Components screen appears but with the entries disabled. The old Replication Server components are replaced with the new ones in the old Replication Server’s directory location. Select **Next**.
 
 1.  The Existing Installation screen confirms that an existing Replication Server installation was found. To proceed with the upgrade, select **Next**.
 
 1.  On the Ready to Install screen, select **Next**.
 
     The remaining screens that appear confirm completion of the installation process and allow you to exit from Stack Builder or StackBuilder Plus.
 
-1.  After installation completes, the publication server of the new Replication Server product is running, connected to the controller database used by Replication Server 6.2. The subscription server might be running at this point. That is an expected outcome of this process.
+1.  After installation completes, the publication server of the new Replication Server product is running, connected to the controller database used by Replication Server 6.2. The subscription server might be running at this point, which is an expected outcome of this process.
 
 1.  Complete the publication server and subscription server configuration file setup.
 
     In the `XDB_HOME/etc` directory, a new set of configuration files for Replication Server version 7 are created. These files are named `xdb_pubserver.conf.new` and `xdb_subserver.conf.new`. The new configuration files contain any new configuration options added for Replication Server 7.
 
     The old configuration files used by Replication Server version 6.2.x remain unchanged as `xdb_pubserver.conf` and `xdb_subserver.conf`.
 
-    Merge the old and new configuration files so that the resulting, active configuration files contain any new Replication Server 7 configuration options as well as any nondefault settings you used with the Replication Server 6.2.x and want to continue to use with Replication Server 7. The final set of active configuration files must be named `xdb_pubserver.conf` and `xdb_subserver.conf`.
+    Merge the old and new configuration files so that the resulting active configuration files contain any new Replication Server 7 configuration options as well as any nondefault settings you used with the Replication Server 6.2.x and want to continue to use with Replication Server 7. The final set of active configuration files must be named `xdb_pubserver.conf` and `xdb_subserver.conf`.
 
-    In the `XDB_HOME/etc/sysconfig` directory, make sure the Replication Server startup configuration file `xdbReplicationServer-62.config` contains the parameter settings you want to use with Replication Server 7. See [Replication Server startup configuration file](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for information on this file.
+    In the `XDB_HOME/etc/sysconfig` directory, make sure the Replication Server startup configuration file `xdbReplicationServer-62.config` contains the parameter settings you want to use with Replication Server 7. See [Replication Server startup configuration file](../../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for more information.
 
 1.  Restart the publication server and the subscription server. See [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server)).
 
 1.  Check the publication server and subscription server log files to verify that no errors occurred (see [Publication and subscription server startup failures](../../10_appendix/02_resolving_problems/02_where_to_look_for_errors/#publication-and-subscription-server-startup-failures)).
 
-1.  Adjust the publication server and subscription server port numbers if necessary.
+1.  If necessary, adjust the publication server and subscription server port numbers.
 
     The Replication Server 7 publication and subscription servers are installed to use the default port numbers `9051` and `9052`, respectively. If the Replication Server 6.2.x replication systems used port numbers other than `9051` and `9052`, then make the changes to correct this inconsistency as described in [Updating the publication and subscription server ports](updating_sub_and_pub_ports).
 
@@ -52,4 +52,4 @@ After upgrading and before using Replication Server, you need to download a JDBC
 You're now ready to use Replication Server 7 to create new replication systems and manage existing ones.
 
 !!! Note
-    **For Windows:** If you give a new admin password during an upgrade, it is ignored. After the upgrade, Replication Server picks the old admin user name and password (which is saved in `edb-replconf`).
+    **For Windows:** If you give a new admin password during an upgrade, it's ignored. After the upgrade, Replication Server picks the old admin user name and password, which is saved in `edb-replconf`.