Merge branch 'release-sqlseattle' of https://github.com/MicrosoftDocs/sql-docs-pr into sql-enclaves

Author: stevestein

docs/linux/sql-server-linux-kubernetes-operator.md

@@ -23,8 +23,6 @@ This article explains the operator global environment variables.
 
 The following example describes a deployment for the `mssql-operator`.
 
-[!INCLUDE[kubernetes-ag-operator-yaml](../includes/kubernetes-ag-operator-yaml.md)]
-
 ## Global environment variables
 
 * `MSSQL_K8S_POD_NAMESPACE` 

docs/linux/sql-server-linux-kubernetes-spec.md

@@ -23,7 +23,6 @@ This article shows how to create the specification, and explains the parameters
 
 The following example of a manifest file describes a Kubernetes specification for SQL Server. Copy the contents of the example into a new file named `sqlservers.yaml` to create the SQL Server availability group StatefulSet in Kubernetes.
 
-[!INCLUDE[kubernetes-ag-sql-statefulset-yaml](../includes/kubernetes-ag-sql-statefulset-yaml.md)]
 
 To deploy the SQL Server instances and create the availability group, run the following command.
 

docs/linux/tutorial-sql-server-ag-kubernetes.md

@@ -59,7 +59,6 @@ To create the storage, create a manifest that describes:
 
 To create the manifest for the storage, make a file named `pvc.yaml`, and copy in the following `.yaml` code.
 
-[!INCLUDE[ag-pvc-manifest](../includes/kubernetes-ag-pvc-yaml.md)]
 
 Next, apply the manifest to the Kubernetes cluster. The following example applies the manifest:
 
@@ -97,7 +96,6 @@ kubectl describe pv
 
 To deploy the operator, create a file named `operator.yaml`, and copy in the following manifest.
 
-[!INCLUDE[kubernetes-ag-operator-yaml](../includes/kubernetes-ag-operator-yaml.md)]
 
 Deploy the operator with the `kubectl apply` command.
 
@@ -130,7 +128,6 @@ To create the specification, create a file named `sqlservers.yaml`.
 
 Copy the manifest below into the file.
 
-[!INCLUDE[kubernetes-ag-sql-statefulset-yaml](../includes/kubernetes-ag-sql-statefulset-yaml.md)]
 
 To deploy the SQL Server instances and create the availability group, run the following command.
 

docs/sql-server/what-s-new-in-sql-server-ver15.md

@@ -40,7 +40,7 @@ Community technology preview (CTP) 2.0 is the first public release of [!INCLUDE[
   - Support for columnstore statistics in `DBCC CLONEDATABASE`
   - New options added to `sp_estimate_data_compression_savings`
   - New `sys.dm_db_page_info` system function returns page information
-  - Always On Availability Groups secondary to primary replica connection redirection
+  - Always On Availability Groups
   - Always Encrypted with secure enclaves
   - SQL Graph features
   - Java language programmability extension
@@ -198,7 +198,9 @@ FROM sys.dm_exec_requests AS d
     AS page_info
 ```
 
-### <a id="ha"></a>Always On Availability Groups secondary to primary replica connection redirection
+### <a id="ha"></a>Always On Availability Groups 
+
+- **Up to five synchronous replicas** – SQL Server 2019 preview increases the limit for synchronous replicas from three (in SQL Server 2017) to five. Configure up to five synchronous replicas (1 primary and up to 4 synchronous secondary replicas) with automatic failover between these replicas.
 
 - **Secondary to primary replica connection redirection**: Allows client application connections to be directed to the primary replica regardless of the target server specified in the connection string. This capability allows connection redirection without a listener. Use Secondary to primary replica connection redirection in the following cases: