Merge pull request #275204 from tomvcassidy/removingPromissoryLinuxNotes

removing promissory linux notes and clarifaction linux limitations

Author: prmerger-automator[bot]

articles/service-fabric/service-fabric-deploy-anywhere.md

@@ -1,20 +1,20 @@
 ---
 title: Overview of Azure and standalone Service Fabric clusters 
-description: You can create Service Fabric clusters on any VMs or computers running Windows Server or Linux. This means you are able to deploy and run Service Fabric applications in any environment where you have a set of Windows Server or Linux computers that are interconnected- on-premises, Microsoft Azure, or with any cloud provider.
+description: Analysis of differences between Azure and standalone Service Fabric clusters on Windows Server and Linux machines.
 ms.topic: conceptual
 ms.author: tomcassidy
 author: tomvcassidy
 ms.service: service-fabric
 ms.custom: linux-related-content
 services: service-fabric
-ms.date: 07/14/2022
+ms.date: 05/13/2024
 ---
 
 # Comparing Azure and standalone Service Fabric clusters on Windows Server and Linux
 
-A Service Fabric cluster is a network-connected set of virtual or physical machines into which your microservices are deployed and managed. A machine or VM that is part of a cluster is called a cluster node. Clusters can scale to thousands of nodes. If you add new nodes to the cluster, Service Fabric rebalances the service partition replicas and instances across the increased number of nodes. Overall application performance improves and contention for access to memory decreases. If the nodes in the cluster are not being used efficiently, you can decrease the number of nodes in the cluster. Service Fabric again rebalances the partition replicas and instances across the decreased number of nodes to make better use of the hardware on each node.
+A Service Fabric cluster is a network-connected set of virtual or physical machines into which your microservices are deployed and managed. A machine or virtual machine (VM) that is part of a cluster is called a cluster node. Clusters can scale to thousands of nodes. If you add new nodes to the cluster, Service Fabric rebalances the service partition replicas and instances across the increased number of nodes. Overall application performance improves and contention for access to memory decreases. If the nodes in the cluster aren't being used efficiently, you can decrease the number of nodes in the cluster. Service Fabric again rebalances the partition replicas and instances across the decreased number of nodes to make better use of the hardware on each node.
 
-Service Fabric allows for the creation of Service Fabric clusters on any VMs or computers running Windows Server or Linux. This means you are able to deploy and run Service Fabric applications in any environment where you have a set of Windows Server or Linux computers that are interconnected, be it on-premises, Microsoft Azure, or with any cloud provider.
+Service Fabric allows for the creation of Service Fabric clusters on any VMs or computers running Windows Server or Linux. However, [standalone clusters](service-fabric-standalone-clusters-overview.md) aren't available on Linux. For more information about the differences in feature support for Windows and Linux, see [Differences between Service Fabric on Linux and Windows](service-fabric-linux-windows-differences.md).
 
 ## Benefits of clusters on Azure
 
@@ -29,7 +29,7 @@ On Azure, we provide integration with other Azure features and services, which m
 
 ## Benefits of standalone clusters
 
-* You are free to choose any cloud provider to host your cluster.
+* You're free to choose any cloud provider to host your cluster.
 * Service Fabric applications, once written, can be run in multiple hosting environments with minimal to no changes.
 * Knowledge of building Service Fabric applications carries over from one hosting environment to another.
 * Operational experience of running and managing Service Fabric clusters carries over from one environment to another.

articles/service-fabric/service-fabric-linux-windows-differences.md

@@ -7,24 +7,24 @@ author: tomvcassidy
 ms.service: service-fabric
 ms.custom: linux-related-content
 services: service-fabric
-ms.date: 07/14/2022
+ms.date: 05/13/2024
 ---
 
 # Differences between Service Fabric on Linux and Windows
 
-There are some features that are supported on Windows, but not yet on Linux. Eventually, the feature sets will be at parity and with each release this feature gap will shrink. The following differences exist between the latest available releases.
+There are some features that are supported on Windows but not on Linux. The following differences exist between the latest available releases:
 
 * Envoy (Reverse Proxy) is in preview on Linux
-* Standalone installer for Linux is not yet available on Linux
+* Standalone installer isn't available on Linux
 * Console redirection (not supported in Linux or Windows production clusters)
 * The Fault Analysis Service (FAS) on Linux
-* DNS service for Service Fabric services (DNS service is supported for containers on Linux)
-* CLI command equivalents of certain PowerShell commands (list below, most of which apply only to standalone clusters)
-* [Differences in log implementation that may affect scalability](service-fabric-concepts-scalability.md#choosing-a-platform)
+* Domain Name System (DNS) service for Service Fabric services (DNS service is supported for containers on Linux)
+* CLI command equivalents of certain PowerShell commands detailed in [PowerShell cmdlets that don't work against a Linux Service Fabric Cluster](#powershell-cmdlets-that-dont-work-against-a-linux-service-fabric-cluster). Most of these cmdlets only apply to standalone clusters.
+* [Differences in log implementation that can affect scalability](service-fabric-concepts-scalability.md#choosing-a-platform)
 * [Difference in Service Fabric Events Channel](service-fabric-diagnostics-overview.md#platform-cluster-monitoring)
 
 
-## PowerShell cmdlets that do not work against a Linux Service Fabric cluster
+## PowerShell cmdlets that don't work against a Linux Service Fabric cluster
 
 * Invoke-ServiceFabricChaosTestScenario
 * Invoke-ServiceFabricFailoverTestScenario