Merge pull request #28743 from tysonn/master

adding site identifier to pageTitle attributes for Acrolinx testing

.acrolinx-config.edn

@@ -1,4 +1,4 @@
-{:allowed-branch-names ["master" "acrolinx-test"]
+{:allowed-branch-names ["master" "acrolinx-test" "release-azure-stack-tp2"]
  :allowed-filename-matches ["articles" "includes"]
 
  :template-header
@@ -13,11 +13,7 @@ Click the scorecard links for each article to review the Acrolinx feedback on gr
    ;; linebreak
    :template-change
    "
-* **Article: ${github/filename}**<br>
-  [Scorecard link](${acrolinx/scorecard})<br>
-  Number of issues: ${acrolinx/flags/total}<br>
-  Score: ${acrolinx/qualityscore}
-
+* **Article: ${github/filename}**: score ${acrolinx/qualityscore}, ${acrolinx/flags/total} issues, [scorecard link](${acrolinx/scorecard}) 
 "
 
  :template-footer

articles/architecture-overview.md

@@ -1,5 +1,5 @@
 <properties 
-	pageTitle="Application Architecture on Microsoft Azure" 
+	pageTitle="Application Architecture on Microsoft Azure | Microsoft Azure" 
 	description="Architecture overview that covers common design patterns" 
 	services="" 
 	documentationCenter="" 

articles/azure-classic-rm.md

@@ -1,5 +1,5 @@
 <properties
-   pageTitle="Resource Manager and Service Management (classic) deployment modes | Azure"
+   pageTitle="Resource Manager and Service Management (classic) deployment modes | Microsoft Azure"
    description="Learn the differences between Resource Manager and classic deployment models."
    services="virtual-network"
    documentationCenter=""
@@ -33,7 +33,7 @@ The documentation for each Azure resource details which service models it can be
 
 It matters for the following reasons:
 
-- The Azure platform features that you use are different across these two models.  For example, resources created using the Resource Manager deployment model (or just Resource Manager) can be created with [Azure Resource Manager templates](resource-group-overview.md/#template-deployment), whereas resources created with the Classic deployment model cannot.
+- The Azure platform features that you use are different across these two models.  For example, resources created using the Resource Manager deployment model (or just Resource Manager) can be created with [Azure Resource Manager templates](resource-group-overview.md#template-deployment), whereas resources created with the Classic deployment model cannot.
 - The individual Azure resource features or behaviors can be different across the two models, or only exist in one model or the other.  For example, load balancing traffic across virtual machines created with the Classic deployment model is *implicit* because virtual machines are members of an Azure Cloud Service, and load is automatically balanced across virtual machines within a cloud service. Virtual machines created using Resource Manager are not members of a cloud service, and a separate Azure Load Balancer resource must be *explicitly* created to load balance traffic across multiple virtual machines.  
 - How you create, configure, and manage your Azure resources is different between these two models.
 - Resources created using one deployment model can't necessarily interoperate with resources created using a different deployment model. For example, Azure Virtual Machines created using one deployment model can only be connected to Azure Virtual Networks created using the same deployment model.    

articles/azure-diagnostics.md

@@ -1,5 +1,5 @@
 <properties
-	pageTitle="Overview of Azure Diagnostics"
+	pageTitle="Overview of Azure Diagnostics | Microsoft Azure"
 	description="Use Azure diagnostics for debugging, measuring performance, monitoring, traffic analysis in cloud services, virtual machines and service fabric"
 	services="multiple"
 	documentationCenter=".net"

articles/azure-government-overview.md

@@ -1,5 +1,5 @@
 <properties 
-   pageTitle="Azure Government Overview" 
+   pageTitle="Azure Government Overview | Microsoft Azure" 
    description="This article provides an overview of the Azure Government Cloud capabilities and the trustworthy design and security used to support compliance applicable to federal, state, and local government organizations and their partners. " 
    services="Azure-Government" 
    documentationCenter=""