DOCSP-21683 fix for legacy terminology (#188)

* DOCSP-21683 fix for legacy terminology

* DOCSP-21683 updates for CR feedback

Author: kanchana-mongodb

source/cloud/connectionstring.txt

@@ -17,7 +17,8 @@
 
      This guide will show you how to set up your Atlas cluster for connections from a client. You will:
 
-       - whitelist your IP address in order to allow access to your Atlas cluster
+       - add your IP address to the IP access list to allow access to 
+         your Atlas cluster
        - locate your connection string and copy it
 
    time: 15
@@ -38,8 +39,8 @@
 
    summary:
      If you have successfully completed this guide, you will now have
-     your IP address in the Atlas whitelist, and an Atlas connection
-     string in your copy buffer.
+     your IP address in the Atlas IP access list, and an Atlas 
+     connection string in your copy buffer.
 
    whats_next:
      - :doc:`/server/drivers`

source/includes/live-migrate-cutover.rst

@@ -28,6 +28,6 @@
 
      - Mark the migration plan as complete.
      - Remove the Application Server subnets from the destination
-       cluster whitelist.
+       cluster IP access list.
      - Remove the MongoDB user that Live Migrate used to import data
        to the destination cluster.

source/includes/steps-find_connection_string.yaml

@@ -20,32 +20,33 @@ content: |
      :figwidth: 328px
 
 ---
-title: Whitelist your IP address and select your connection method
+title: Add your IP address to the IP access list and select your connection method
 ref: bind_db
 level: 4
 stepnum: 3
 content: |
 
   In the :guilabel:`Setup connection security` step in the modal
-  window, check to make sure your IP address is
-  in the whitelist for Atlas connections. If it is not, add it.
+  window, check to make sure your IP address is in the IP access list 
+  for Atlas connections. If it is not, add it.
 
   The following Atlas screenshot shows the options for adding IP
   addresses in the Atlas UI:
 
   .. figure:: /images/connectionstringwhitelist.png
      :figwidth: 600px
 
-  If your cluster already has one or more IP Whitelist entries you
-  will not have access to the button to add your IP address in the
+  If your cluster already has one or more IP access list entries, you
+  won't have access to the button to add your IP address in the
   modal. Instead, use the following procedure to add your IP address
-  to the whitelist:
+  to the IP access list:
   
   1. Exit the modal window.
 
-  #. Click the :guilabel:`Security` tab in the Atlas UI.
+  #. Click :guilabel:`Network Access` under the :guilabel:`Security` 
+     section in the Atlas UI.
 
-  #. Click the :guilabel:`IP Whitelist` tab.
+  #. Click the :guilabel:`IP Access List` tab.
 
   #. Click the green :guilabel:`Add IP Address` button.
 
@@ -55,9 +56,9 @@ content: |
 
   #. Click the :guilabel:`Connect` button and proceed.
 
-  For more information on whitelisting IP addresses, see
-  `Configure Whitelist Entries
-  <https://docs.atlas.mongodb.com/security-whitelist/>`_
+  To learn more about adding IP addresses to the IP access list, see
+  `Configure IP Access List Entries
+  <https://www.mongodb.com/docs/security/ip-access-list/>`_
   in the Atlas documentation.
 
 ---

source/includes/steps-migrate-to-atlas.yaml

@@ -37,7 +37,7 @@ ref: click-ready-migrate
 level: 4
 stepnum: 3
 ---
-title: Whitelist the Atlas Live Migration Service on your AWS source cluster.
+title: Add the IP address for the Atlas Live Migration Service on your AWS source cluster.
 ref: whitelist-migration-service
 level: 4
 stepnum: 4
@@ -51,9 +51,9 @@ content: |
 
    AWS EC2 servers are protected from unauthorized network access using
    `Security Groups <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-rules-reference.html>`_.
-   To whitelist new IP address ranges, either create a new Security Group, or
-   modify your existing Security Group to permit inbound network access
-   from the displayed IP address ranges. 
+   To add new IP address ranges to the IP access list, either create a 
+   new Security Group, or modify your existing Security Group to permit 
+   inbound network access from the displayed IP address ranges. 
 
    Here is an example security group that grants access to Atlas Live Migration Service.