Pre OSS commit

Author: nginx

content/includes/acm/how-to/access-acm-ui.md

@@ -1,7 +1,7 @@
 
 This guide provides instructions for completing tasks using the API Connectivity Manager user interface (UI).
 
-To access the UI, go to the FQDN of your NGINX Management Suite host and log in. On the Launchpad menu, select "API Connectivity Manager."
+To access the UI, go to the FQDN of your NGINX Instance Manager host and log in. On the Launchpad menu, select "API Connectivity Manager."
 
 <!-- Do not remove. Keep this code at the bottom of the include -->
 <!-- DOCS-1004 -->

content/includes/acm/installation/enable-start-nms-acm.md

@@ -12,9 +12,9 @@ To enable and start the API Connectivity Manager services, take the following st
     sudo systemctl start nms-acm
     ```
 
-    NGINX Management Suite components started this way run by default as the non-root `nms` user inside the `nms` group, both of which are created during installation.
+    NGINX Instance Manager components started this way run by default as the non-root `nms` user inside the `nms` group, both of which are created during installation.
 
-3. To verify the NGINX Management Suite services are running, run the following command:
+3. To verify the NGINX Instance Manager services are running, run the following command:
 
     ```bash
     ps aufx | grep nms
@@ -27,7 +27,7 @@ To enable and start the API Connectivity Manager services, take the following st
    ```
 
 <details close>
-<summary><i class="fa-solid fa-circle-info"></i> Overview: NGINX Management Suite services</summary>
+<summary><i class="fa-solid fa-circle-info"></i> Overview: NGINX Instance Manager services</summary>
 
 {{< include "nms/nms-services.md" >}}
 

content/includes/acm/installation/install-acm-dev-portal.md

@@ -18,7 +18,7 @@ The Developer Portal has the following platform requirements:
 
 ### Installation Steps
 
-1. Follow the steps to [add the NGINX Management Suite Repo](#add-yum-apt) to Yum or Apt.
+1. Follow the steps to [add the NGINX Instance Manager Repo](#add-yum-apt) to Yum or Apt.
 
 1. Run the following command(s) for your Linux distribution to install the Developer Portal:
 

content/includes/acm/installation/install-acm-offline.md

@@ -10,9 +10,9 @@
    sudo yum --nogpgcheck install /home/user/nms-api-connectivity-manager_<version>.x86_64.rpm
    ```
 
-3. (Optional) If you used a custom address, username, or password or enabled TLS when installing ClickHouse, follow the steps in the [Configure ClickHouse]({{< relref "/nim/admin-guide/getting-started/configure-clickhouse.md" >}}) guide to update the `nms.conf` file. If you don't do so, NGINX Management Suite won't be able to connect to ClickHouse.
+3. (Optional) If you used a custom address, username, or password or enabled TLS when installing ClickHouse, follow the steps in the [Configure ClickHouse]({{< relref "/nim/admin-guide/getting-started/configure-clickhouse.md" >}}) guide to update the `nms.conf` file. If you don't do so, NGINX Instance Manager won't be able to connect to ClickHouse.
 
-4. (Optional) If you use Vault, follow the steps in the [Configure Vault]({{< relref "/nim/admin-guide/getting-started/configure-vault.md" >}}) guide to update the `nms.conf` file. If you don't do so, NGINX Management Suite won't be able to connect to Vault.
+4. (Optional) If you use Vault, follow the steps in the [Configure Vault]({{< relref "/nim/admin-guide/getting-started/configure-vault.md" >}}) guide to update the `nms.conf` file. If you don't do so, NGINX Instance Manager won't be able to connect to Vault.
 
 {{%/tab%}}
 {{%tab name="Debian, Ubuntu, and Deb-Based"%}}
@@ -25,14 +25,14 @@
    sudo apt-get install -f /home/user/nms-api-connectivity-manager_<version>_amd64.deb
    ```
 
-3. (Optional) If you used a custom address, username, or password or enabled TLS when installing ClickHouse, follow the steps in the [Configure ClickHouse]({{< relref "/nim/admin-guide/getting-started/configure-clickhouse.md" >}}) guide to update the `nms.conf` file. If you don't do so, NGINX Management Suite won't be able to connect to ClickHouse.
+3. (Optional) If you used a custom address, username, or password or enabled TLS when installing ClickHouse, follow the steps in the [Configure ClickHouse]({{< relref "/nim/admin-guide/getting-started/configure-clickhouse.md" >}}) guide to update the `nms.conf` file. If you don't do so, NGINX Instance Manager won't be able to connect to ClickHouse.
 
-4. (Optional) If you use Vault, follow the steps in the [Configure Vault]({{< relref "/nim/admin-guide/getting-started/configure-vault.md" >}}) guide to update the `nms.conf` file. If you don't do so, NGINX Management Suite won't be able to connect to Vault.
+4. (Optional) If you use Vault, follow the steps in the [Configure Vault]({{< relref "/nim/admin-guide/getting-started/configure-vault.md" >}}) guide to update the `nms.conf` file. If you don't do so, NGINX Instance Manager won't be able to connect to Vault.
 
 {{%/tab%}}
 {{</tabs>}}
 
-When installing API Connectivity Manager, you may need a newer version of NGINX Management Suite. The installation process will notify you of any version requirements before installing API Connectivity Manager and any dependent packages, including NGINX Management Suite. You may cancel the installation process if a backup of the NGINX Management Suite is needed before upgrading.
+When installing API Connectivity Manager, you may need a newer version of NGINX Instance Manager. The installation process will notify you of any version requirements before installing API Connectivity Manager and any dependent packages, including NGINX Instance Manager. You may cancel the installation process if a backup of the NGINX Instance Manager is needed before upgrading.
 
 5. Enable the API Connectivity Manager services:
 
@@ -46,9 +46,9 @@ When installing API Connectivity Manager, you may need a newer version of NGINX
     sudo systemctl start nms-acm
     ```
 
-    NGINX Management Suite components started this way run by default as the non-root `nms` user inside the `nms` group, both of which are created during installation.
+    NGINX Instance Manager components started this way run by default as the non-root `nms` user inside the `nms` group, both of which are created during installation.
 
-7. To verify the NGINX Management Suite services are running, run the following command:
+7. To verify the NGINX Instance Manager services are running, run the following command:
 
     ```bash
     ps aufx | grep nms

content/includes/acm/installation/install-acm.md

@@ -13,7 +13,7 @@ To install the latest version of API Connectivity Manager, run the following com
   sudo apt-get install nms-api-connectivity-manager
   ```
 
-When installing API Connectivity Manager, you may need a newer version of NGINX Management Suite. The installation process will notify you of any version requirements before installing API Connectivity Manager and any dependent packages, including NGINX Management Suite. You may cancel the installation process if a backup of the NGINX Management Suite is needed before upgrading.
+When installing API Connectivity Manager, you may need a newer version of NGINX Instance Manager. The installation process will notify you of any version requirements before installing API Connectivity Manager and any dependent packages, including NGINX Instance Manager. You may cancel the installation process if a backup of the NGINX Instance Manager is needed before upgrading.
 
 <!-- Do not remove. Keep this code at the bottom of the include -->
 <!-- DOCS-1016 -->

content/includes/acm/installation/upgrade-acm-offline.md

@@ -25,7 +25,7 @@ To upgrade API Connectivity Manager in an offline environment, take the followin
 {{%/tab%}}
 {{</tabs>}}
 
-When installing API Connectivity Manager, you may need a newer version of NGINX Management Suite. The installation process will notify you of any version requirements before installing API Connectivity Manager and any dependent packages, including NGINX Management Suite. You may cancel the installation process if a backup of the NGINX Management Suite is needed before upgrading.
+When installing API Connectivity Manager, you may need a newer version of NGINX Instance Manager. The installation process will notify you of any version requirements before installing API Connectivity Manager and any dependent packages, including NGINX Instance Manager. You may cancel the installation process if a backup of the NGINX Instance Manager is needed before upgrading.
 
 3. Enable the API Connectivity Manager services:
 
@@ -39,9 +39,9 @@ When installing API Connectivity Manager, you may need a newer version of NGINX
     sudo systemctl restart nms-acm
     ```
 
-    NGINX Management Suite components started this way run by default as the non-root `nms` user inside the `nms` group, both of which are created during installation.
+    NGINX Instance Manager components started this way run by default as the non-root `nms` user inside the `nms` group, both of which are created during installation.
 
-5. To verify the NGINX Management Suite services are running, run the following command:
+5. To verify the NGINX Instance Manager services are running, run the following command:
 
     ```bash
     ps aufx | grep nms

content/includes/acm/installation/upgrade-acm.md

@@ -8,7 +8,7 @@
    sudo yum update nms-api-connectivity-manager
    ```
 
-    When installing API Connectivity Manager, you may need a newer version of NGINX Management Suite. The installation process will notify you of any version requirements before installing API Connectivity Manager and any dependent packages, including NGINX Management Suite. You may cancel the installation process if a backup of the NGINX Management Suite is needed before upgrading.
+    When installing API Connectivity Manager, you may need a newer version of NGINX Instance Manager. The installation process will notify you of any version requirements before installing API Connectivity Manager and any dependent packages, including NGINX Instance Manager. You may cancel the installation process if a backup of the NGINX Instance Manager is needed before upgrading.
 
 2. Enable the API Connectivity Manager services:
 
@@ -22,9 +22,9 @@
     sudo systemctl restart nms-acm
     ```
 
-    NGINX Management Suite components started this way run by default as the non-root `nms` user inside the `nms` group, both of which are created during installation.
+    NGINX Instance Manager components started this way run by default as the non-root `nms` user inside the `nms` group, both of which are created during installation.
 
-4. To verify the NGINX Management Suite services are running, run the following command:
+4. To verify the NGINX Instance Manager services are running, run the following command:
 
     ```bash
     ps aufx | grep nms
@@ -47,7 +47,7 @@
    sudo apt-get install --only-upgrade nms-api-connectivity-manager
    ```
 
-   When installing API Connectivity Manager, you may need a newer version of NGINX Management Suite. The installation process will notify you of any version requirements before installing API Connectivity Manager and any dependent packages, including NGINX Management Suite. You may cancel the installation process if a backup of the NGINX Management Suite is needed before upgrading.
+   When installing API Connectivity Manager, you may need a newer version of NGINX Instance Manager. The installation process will notify you of any version requirements before installing API Connectivity Manager and any dependent packages, including NGINX Instance Manager. You may cancel the installation process if a backup of the NGINX Instance Manager is needed before upgrading.
 
 2. Enable the API Connectivity Manager services:
 
@@ -61,9 +61,9 @@
     sudo systemctl restart nms-acm
     ```
 
-    NGINX Management Suite components started this way run by default as the non-root `nms` user inside the `nms` group, both of which are created during installation.
+    NGINX Instance Manager components started this way run by default as the non-root `nms` user inside the `nms` group, both of which are created during installation.
 
-4. To verify the NGINX Management Suite services are running, run the following command:
+4. To verify the NGINX Instance Manager services are running, run the following command:
 
     ```bash
     ps aufx | grep nms

content/includes/acm/webui-acm-login.md

@@ -2,4 +2,4 @@
 docs: DOCS-1189
 ---
 
-In a web browser, go to the FQDN for your NGINX Management Suite host and log in. Then, from the Launchpad menu, select **API Connectivity Manager**.
+In a web browser, go to the FQDN for your NGINX Instance Manager host and log in. Then, from the Launchpad menu, select **API Connectivity Manager**.

content/includes/agent/installation/install-agent-api.md

@@ -1,4 +1,4 @@
-**Note**: To complete this step, make sure that `gpg` is installed on your system. You can install NGINX Agent using various command-line tools like `curl` or `wget`. If your NGINX Management Suite host is not set up with valid TLS certificates, you can use the insecure flags provided by those tools. See the following examples:
+**Note**: To complete this step, make sure that `gpg` is installed on your system. You can install NGINX Agent using various command-line tools like `curl` or `wget`. If your NGINX Instance Manager host is not set up with valid TLS certificates, you can use the insecure flags provided by those tools. See the following examples:
 
 {{<tabs name="install-agent-api">}}
 

content/includes/installation/access-web-ui.md

@@ -2,6 +2,6 @@
 docs: DOCS-1241
 ---
 
-To access the NGINX Management Suite web interface, open a web browser and go to `https://<NMS_FQDN>`, replacing `<NMS_FQDN>` with the Fully Qualified Domain Name of your NGINX Management Suite host.
+To access the NGINX Instance Manager web interface, open a web browser and go to `https://<NMS_FQDN>`, replacing `<NMS_FQDN>` with the Fully Qualified Domain Name of your NGINX Instance Manager host.
 
 The default administrator username is `admin`, and the generated password was displayed in the terminal during installation. If you'd like to change this password, refer to the "[Set or Change User Passwords]({{< relref "/nim/admin-guide/authentication/basic-auth/set-up-basic-authentication.md#set-basic-passwords-script" >}}) section in the Basic Authentication topic.