Edits

pauljewellmsft · pauljewellmsft · commit 582d4b8b9e56 · 2024-11-25T09:40:52.000-05:00
diff --git a/articles/fxt-edge-filer/mount-clients.md b/articles/fxt-edge-filer/mount-clients.md
@@ -11,7 +11,7 @@ ms.date: 06/20/2019
 # Tutorial: Mount the cluster
 
 > [!NOTE]
-> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information about the retirement.
+> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
 
 This tutorial teaches you how to mount NFS clients to the Azure FXT Edge Filer cluster. Clients mount the virtual namespace paths that you assigned when you added back-end storage.
 
diff --git a/articles/fxt-edge-filer/network-power.md b/articles/fxt-edge-filer/network-power.md
@@ -11,7 +11,7 @@ ms.date: 07/01/2019
 # Tutorial: Make network connections and supply power to the Azure FXT Edge Filer node
 
 > [!NOTE]
-> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information about the retirement.
+> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
 
 This tutorial teaches you how to cable the network connections for an Azure FXT Edge Filer hardware node.
 
diff --git a/articles/fxt-edge-filer/node-password.md b/articles/fxt-edge-filer/node-password.md
@@ -11,7 +11,7 @@ ms.date: 06/20/2019
 # Tutorial: Set hardware passwords
 
 > [!NOTE]
-> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information about the retirement.
+> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
 
 The first time you power up an Azure FXT Edge Filer node, you must set a root password. The hardware nodes are not shipped with a default password.
 
diff --git a/articles/fxt-edge-filer/port-list.md b/articles/fxt-edge-filer/port-list.md
@@ -11,11 +11,11 @@ ms.date: 05/26/2021
 # Required network ports
 
 > [!NOTE]
-> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information about the retirement.
+> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
 
 This list shows TCP/UDP ports required by FXT cluster environments. Configure any firewalls you use to make sure these ports are accessible.
 
-Your system's specific requirements will vary depending on what kind of back-end storage you use.
+Your system's specific requirements vary depending on what kind of back-end storage you use.
 
 For more information, contact Microsoft Service and Support.
 
@@ -46,7 +46,7 @@ Outbound NFS ports:
 | TCP/UDP | 111         | RPCBIND  |
 | TCP/UDP | 2049        | NFS      |
 
-Outbound NFS port traffic varies depending on the kind of storage used as a core filer. (Some systems do not use port 2049, though it is common enough to be listed here. All clusters need access on port 111.) Check the documentation for your storage systems or use the query technique described below in [Additional port requirements](#additional-port-requirements).
+Outbound NFS port traffic varies depending on the kind of storage used as a core filer. (Some systems don't use port 2049, though it's common enough to be listed here. All clusters need access on port 111.) Check the documentation for your storage systems or use the query technique described below in [Additional port requirements](#additional-port-requirements).
 
 Some outbound NFS traffic from FXT nodes uses ephemeral ports. Outbound FXT traffic above well-known ports should not be restricted at the transport level.
 
@@ -78,7 +78,7 @@ Some outbound NFS traffic from FXT nodes uses ephemeral ports. Outbound FXT traf
 
 Your core filers might require access on additional ports. This requirement varies depending on the type of storage used.
 
-You can use the `rpcinfo` command to learn which ports are used by a particular server. Issue this command from a client system that is not firewalled:
+You can use the `rpcinfo` command to learn which ports are used by a particular server. Issue this command from a client system that isn't firewalled:
 
 `rpcinfo -p <server_IP_address>`
 
diff --git a/articles/fxt-edge-filer/power-off.md b/articles/fxt-edge-filer/power-off.md
@@ -11,7 +11,7 @@ ms.date: 07/01/2019
 # How to safely power off Azure FXT Edge Filer hardware
 
 > [!NOTE]
-> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information about the retirement.
+> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
 
 Although you can use the physical power button to switch on an individual node, you should not use it to shut down the unit under normal circumstances.
 
diff --git a/articles/fxt-edge-filer/specs.md b/articles/fxt-edge-filer/specs.md
@@ -11,7 +11,7 @@ ms.date: 06/20/2019
 # Azure FXT Edge Filer specifications
 
 > [!NOTE]
-> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information about the retirement.
+> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
 
 This article explains the hardware specifications for Azure FXT Edge Filer hardware nodes. In practice, three or more nodes are configured together to provide the clustered cache system.
 
diff --git a/articles/fxt-edge-filer/support-ticket.md b/articles/fxt-edge-filer/support-ticket.md
@@ -11,7 +11,7 @@ ms.date: 07/10/2019
 # Open a support ticket for the Azure FXT Edge Filer
 
 > [!NOTE]
-> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information about the retirement.
+> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
 
 This article explains how to get help with your Azure FXT Edge Filer system.
 
diff --git a/articles/fxt-edge-filer/supported-ciphers.md b/articles/fxt-edge-filer/supported-ciphers.md
@@ -11,7 +11,7 @@ ms.date: 05/20/2021
 # Supported encryption standards for Azure FXT Edge Filer
 
 > [!NOTE]
-> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information about the retirement.
+> **Action Required:** Azure FXT Edge Filer will be retired on December 31, 2026. Please remove all Azure FXT Edge Filer resources by December 31, 2026. Visit https://aka.ms/fxtretirementfaq for more information.
 
 This document describes encryption standards needed for Azure FXT Edge Filer. These standards are implemented as of the operating system version 5.1.1.2.
 
