Updating obsolete network usage to connectivity

Author: OlufunkeMoronfolu

content/en/docs/deployment/mendix-cloud-deploy/access-restrictions.md

@@ -104,7 +104,7 @@ To apply access restrictions to a specific application environment, follow these
 
 1. From [Apps](https://sprintr.home.mendix.com), go to the app's **Environments** page.
 2. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the desired environment.
-3. Go to the **Network** tab.
+3. Go to the **Connectivity** tab.
 4. Navigate to the [Path Based Access Restrictions](/developerportal/deploy/environments-details/#path-based-restrictions) section to apply access restrictions to a single environment.
 
 {{% alert color="info" %}}
@@ -174,7 +174,7 @@ To apply IP restrictions to a specific application environment, follow these ste
 
 1. From [Apps](https://sprintr.home.mendix.com), go to the app's **Environments** page.
 2. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the desired environment.
-3. Go to the **Network** tab.
+3. Go to the **Connectivity** tab.
 4. Navigate to the [IP Access Restrictions](/developerportal/deploy/environments-details/#ip-access-restrictions) section to apply access restrictions to a single environment.
 
 {{% alert color="info" %}}
@@ -199,14 +199,15 @@ To restrict access to the app to an IP range, follow these steps:
 5. Add one or more IP ranges to the **Denied IP Profiles**.
 
 6. Save the access restriction profile.
-7. Go to the **Deploy** tab of the **Environments** page. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the desired environment.
-8. Switch to the **Network** tab.
-9. Select the top-level path (`/`) and click **Edit**.
+7. Go to the **Overview** tab on the **Environments** page.
+8. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the desired environment.
+9. Switch to the **Connectivity** tab.
+10. Select the top-level path (`/`) and click **Edit**.
 
     {{% alert color="info" %}}Any path below this path that does not have an explicit restriction will inherit this access restriction profile.{{% /alert %}}
 
-10. Select **Custom Profile for Client Certificates and/or IP ranges** as the **New Restriction Type**.
-11. Select your access restriction profile as the **New Restriction Profile**, and save it.
+11. Select **Custom Profile for Client Certificates and/or IP ranges** as the **New Restriction Type**.
+12. Select your access restriction profile as the **New Restriction Profile**, and save it.
 
 ### Example Scenario 2 – Back-End Administration with Third-Party Web Service Integrations
 
@@ -227,9 +228,10 @@ To add this additional access restriction profile, follow these steps:
 4. Create a new access restriction profile.
 5. Upload the certificate of the internal CA that is used to sign the client certificates.
 6. Save the new access restriction profile.
-7. Go to the **Deploy** tab of the **Environments** page. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the desired environment.
-8. Switch to the **Network** tab.
-9. Edit the `/ws/` path of the environment to apply the new access restriction profile. This overrides the default profile (for the top level `/`) for the selected path (`/ws/`).
+7. Go to the **Overview** tab on the **Environments** page.
+8. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the desired environment.
+9. Switch to the **Connectivity** tab.
+10. Edit the `/ws/` path of the environment to apply the new access restriction profile. This overrides the default profile (for the top level `/`) for the selected path (`/ws/`).
 
 {{% alert color="info" %}}
 If the `/ws/` path should still be reachable from the office location without using a client certificate, add the IP ranges of the office location to the profile used for `/ws/`.

content/en/docs/deployment/mendix-cloud-deploy/environments-details.md

@@ -16,7 +16,7 @@ To open the **Environment Details** page, go to [Apps](https://sprintr.home.mend
 
 {{% alert color="info" %}}You must have permissions for **Transport Rights** to view the **Environment Details** page. For details on configuring permissions, see [Node Permissions](/developerportal/deploy/node-permissions/).{{% /alert %}}
 
-The **Environment Details** page shows information about the selected environment and includes eight tabs: **General**, **Model Options**, **Network**, **Log Levels**, **Runtime**, **Maintenance**, **Tags**, and **Services**. You can also use this page to manage and debug several aspects of the environment.
+The **Environment Details** page shows information about the selected environment and includes nine tabs: **General**, **Model Options**, **Network**, **Connectivity**, **Log Levels**, **Runtime**, **Maintenance**, **Tags**, and **Services**. You can also use this page to manage and debug several aspects of the environment.
 
 ## Actions {#actions}
 

content/en/docs/marketplace/platform-supported-content/modules/document-generation/installation-configuration.md

@@ -79,9 +79,9 @@ To allow the module to send and receive document generation requests on your Men
 
     2. On the **Overview** tab, click **Details** for the respective environment.
 
-    3. In the specific **Environment Details** page, select the **Network** tab.
+    3. In the specific **Environment Details** page, select the **Connectivity** tab.
 
-    4. Scroll down to **Path Based Access Restrictions** and click **Add**. The **Edit Path Based Access Restriction** dialog box opens.
+    4. Scroll down to **Path Based Access Restrictions** and click **Add**. The **New Path Based Access Restriction** dialog box opens.
 
     5. Fill in the fields as follows:
         * In the **Path** field, enter */docgen/*.

content/en/docs/releasenotes/deployment/mendix-cloud/2017.md

@@ -130,7 +130,7 @@ weight: 10
 
 * For all apps running on the Mendix Cloud, the following HTTP request headers are now available: `SSL-Protocol` (possible values: `TLSv1`, `TLSv1.1`, `TLSv1.2`) and `SSL-Cipher` (for example, `ECDHE-RSA-AES256-GCM-SHA384`). These can be used to block login attempts (for example, `TLSv1` connections). *(Please note that these release notes previously stated the header name was `SSL-Version`, but it should have been `SSL-Protocol`.)*
 * Modern browsers are aggressively caching static HTML resources, which can lead to user problems after deploying new versions of applications. Clearing the cache can solve this, but that is a bad user experience. So, for all apps running on Mendix Cloud v3, we have added an explicit `no-cache` header to the resources `/` and `/index.html`, `/login.html`, and `/index[0-9].html`. For Mendix Cloud v4, an `expires` with a negative value was already used, so no changes are required there. We believe this change eliminates most of the browser caching issues we have seen so far.
-* You can now restrict access to your Mendix Cloud v4 applications based on IP ranges. This is available for all Mendix Cloud v4 regions and can be configured from the **Network** tab of your cloud environment.
+* You can now restrict access to your Mendix Cloud v4 applications based on IP ranges. This is available for all Mendix Cloud v4 regions and can be configured from the **Connectivity** tab of your cloud environment.
 
 #### Fixes