Merge pull request #278182 from alexbuckgit/alexbuckgit/docutune-autopr-20240613-184702-7035328-ignore-build

[BULK] - DocuTune v1.4.1 - Standardize formatting of abbreviations (part 5)

Author: v-shils

articles/machine-learning/v1/how-to-secure-web-service.md

@@ -18,7 +18,7 @@ ms.custom: UpdateFrequency5, cliv1, sdkv1
 
 This article shows you how to secure a web service that's deployed through Azure Machine Learning.
 
-You use [HTTPS](https://en.wikipedia.org/wiki/HTTPS) to restrict access to web services and secure the data that clients submit. HTTPS helps secure communications between a client and a web service by encrypting communications between the two. Encryption uses [Transport Layer Security (TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security). TLS is sometimes still referred to as *Secure Sockets Layer* (SSL), which was the predecessor of TLS.
+You use [HTTPS](https://en.wikipedia.org/wiki/HTTPS) to restrict access to web services and secure the data that clients submit. HTTPS helps secure communications between a client and a web service by encrypting communications between the two. Encryption uses [Transport Layer Security (TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security). TLS is sometimes still referred to as *Secure Sockets Layer (SSL)*, which was the predecessor of TLS.
 
 > [!TIP]
 > The Azure Machine Learning SDK uses the term "SSL" for properties that are related to secure communications. This doesn't mean that your web service doesn't use *TLS*. SSL is just a more commonly recognized term.

articles/mysql/flexible-server/concepts-accelerated-logs.md

@@ -41,7 +41,7 @@ Database servers with mission-critical workloads demand robust performance, requ
 
 ## Limitations
 
-- The accelerated logs feature can't be enabled on servers that have [Customer Managed Keys](./concepts-customer-managed-key.md)  (CMK) enabled.
+- The accelerated logs feature can't be enabled on servers that have [Customer Managed Keys (CMK)](./concepts-customer-managed-key.md) enabled.
 
 - The Accelerated logs feature is currently available only in specific regions. [Learn more about supported regions](#regions).
 

articles/mysql/flexible-server/concepts-data-in-replication.md

@@ -61,7 +61,7 @@ The parameter `replicate_wild_ignore_table` creates a replication filter for tab
 
 ### Generated Invisible Primary Key
 
-For MySQL version 8.0 and above, [Generated Invisible Primary Keys](https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html)(GIPK) is enabled by default for all the Azure Database for MySQL flexible server instances. MySQL 8.0+ servers adds the invisible column *my_row_id* to the tables and a primary key on that column, where the InnoDB table is created without an explicit primary key. This feature, when enabled may impact some of the data-in replication use cases, as described below:
+For MySQL version 8.0 and above, [Generated Invisible Primary Keys (GIPK)](https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html) is enabled by default for all the Azure Database for MySQL flexible server instances. MySQL 8.0+ servers adds the invisible column *my_row_id* to the tables and a primary key on that column, where the InnoDB table is created without an explicit primary key. This feature, when enabled may impact some of the data-in replication use cases, as described below:
 
 - Data-in replication fails with replication error: “**ERROR 1068 (42000): Multiple primary key defined**” if source server creates a Primary key on the table without Primary Key. For mitigation, run the following sql command, skip replication error and restart [data-in replication](how-to-data-in-replication.md). 
 

articles/mysql/flexible-server/concepts-limitations.md

@@ -25,7 +25,7 @@ This article describes limitations in Azure Database for MySQL flexible server.
 Azure Database for MySQL flexible server supports tuning the values of server parameters. Some parameters' min and max values (ex. `max_connections`, `join_buffer_size`, `query_cache_size`) are determined by the compute tier and before you compute the size of the server. Refer to [server parameters](./concepts-server-parameters.md) for more information about these limits.
 
 ### Generated Invisible Primary Keys
-For MySQL version 8.0 and above, [Generated Invisible Primary Keys](https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html)(GIPK) is enabled by default for all Azure Database for MySQL flexible server instances. MySQL 8.0+ servers add the invisible column *my_row_id* to the tables and a primary key on that column, where the InnoDB table is created without an explicit primary key. For this reason, you can't create a table having a column named *my_row_id* unless the table creation statement also specifies an explicit primary key. [Learn more](https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html).
+For MySQL version 8.0 and above, [Generated Invisible Primary Keys (GIPK)](https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html) is enabled by default for all Azure Database for MySQL flexible server instances. MySQL 8.0+ servers add the invisible column *my_row_id* to the tables and a primary key on that column, where the InnoDB table is created without an explicit primary key. For this reason, you can't create a table having a column named *my_row_id* unless the table creation statement also specifies an explicit primary key. [Learn more](https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html).
 By default, GIPKs are shown in the output of [SHOW CREATE TABLE](https://dev.mysql.com/doc/refman/8.0/en/show-create-table.html), [SHOW COLUMNS](https://dev.mysql.com/doc/refman/8.0/en/show-columns.html), and [SHOW INDEX](https://dev.mysql.com/doc/refman/8.0/en/show-index.html), and are visible in the Information Schema [COLUMNS](https://dev.mysql.com/doc/refman/8.0/en/information-schema-columns-table.html) and [STATISTICS](https://dev.mysql.com/doc/refman/8.0/en/information-schema-statistics-table.html) tables.
 For more details on GIPK and its use cases with [Data-in-Replication](./concepts-data-in-replication.md) in Azure Database for MySQL flexible server, refer to [GIPK with Data-in-Replication](./concepts-data-in-replication.md#generated-invisible-primary-key). 
 
@@ -130,5 +130,3 @@ For the complete list of feature comparisons between Azure Database for MySQL si
 - Understand [what's available for compute and storage options in flexible server](concepts-service-tiers-storage.md)
 - Learn about [Supported MySQL Versions](concepts-supported-versions.md)
 - Quickstart: [Use the Azure portal to create an Azure Database for MySQL flexible server instance](quickstart-create-server-portal.md)
-
-

articles/notification-hubs/notification-hubs-push-notification-security.md

@@ -23,7 +23,7 @@ This topic describes the security model of Azure Notification Hubs.
 
 ## Shared Access Signature security
 
-Notification Hubs implements an entity-level security scheme called a *Shared Access Signature* (SAS). Each rule contains a name, a key value (shared secret), and a set of rights, as explained later in [Security claims](#security-claims). 
+Notification Hubs implements an entity-level security scheme called a *Shared Access Signature (SAS)*. Each rule contains a name, a key value (shared secret), and a set of rights, as explained later in [Security claims](#security-claims). 
 
 When creating a hub, two rules are automatically created: one with **Listen** rights (that the client app uses) and one with **all** rights (that the app backend uses):
 

articles/operator-nexus/concepts-nexus-kubernetes-placement.md

@@ -15,7 +15,7 @@ Operator Nexus instances are deployed at the customer premises. Each instance
 comprises one or more racks of bare metal servers.
 
 When a user creates a Nexus Kubernetes Cluster (NKS), they specify a count and
-a [stock keeping unit](./reference-nexus-kubernetes-cluster-sku.md) (SKU) for
+a [stock keeping unit (SKU)](./reference-nexus-kubernetes-cluster-sku.md) for
 virtual machines (VM) that make up the Kubernetes Control Plane and one or more
 Agent Pools. Agent Pools are the set of Worker Nodes on which a customer's
 containerized network functions run.

articles/orbital/satellite-imagery-with-orbital-ground-station.md

@@ -18,7 +18,7 @@ This article is a comprehensive walk-through showing how to use the [Azure Orbit
 
 Aqua is a polar-orbiting spacecraft launched by NASA in 2002. Data from all science instruments aboard Aqua is downlinked to the Earth using direct broadcast over the X-band in near real-time. More information about Aqua can be found on the [Aqua Project Science](https://aqua.nasa.gov/) website. 
 
-Using AOGS, we capture the Aqua broadcast when the satellite is within line of sight of a ground station by scheduling a *contact*. A *contact* is time reserved at a ground station to communicate with a satellite. During the contact, the ground station orients its antenna towards Aqua and captures the direct broadcast data. The captured data is sent to an Azure VM as a data stream and processed using the [Real-Time Software Telemetry Processing System](http://directreadout.sci.gsfc.nasa.gov/index.cfm?section=technology&page=NISGS&subpage=NISFES&sub2page=RT-STPS&sub3Page=overview)(RT-STPS) tool provided by the [Direct Readout Laboratory](http://directreadout.sci.gsfc.nasa.gov/)(DRL) which generates a Level-0 product. This Level-0 product is processed further using DRL's [International Planetary Observation Processing Package](https://directreadout.sci.gsfc.nasa.gov/?id=dspContent&cid=68)(IPOPP) tool to produce higher level products.
+Using AOGS, we capture the Aqua broadcast when the satellite is within line of sight of a ground station by scheduling a *contact*. A *contact* is time reserved at a ground station to communicate with a satellite. During the contact, the ground station orients its antenna towards Aqua and captures the direct broadcast data. The captured data is sent to an Azure VM as a data stream and processed using the [Real-Time Software Telemetry Processing System](http://directreadout.sci.gsfc.nasa.gov/index.cfm?section=technology&page=NISGS&subpage=NISFES&sub2page=RT-STPS&sub3Page=overview)(RT-STPS) tool provided by the [Direct Readout Laboratory (DRL)](http://directreadout.sci.gsfc.nasa.gov/) which generates a Level-0 product. This Level-0 product is processed further using DRL's [International Planetary Observation Processing Package (IPOPP)](https://directreadout.sci.gsfc.nasa.gov/?id=dspContent&cid=68) tool to produce higher level products.
 
 In this tutorial, we will follow these steps to collect and process Aqua data:
 
@@ -213,4 +213,3 @@ To easily deploy downstream components necessary to receive and process spacebor
 For an end-to-end implementation that involves extracting, loading, transforming, and analyzing spaceborne data by using geospatial libraries and AI models with Azure Synapse Analytics, see: 
 
 - [Spaceborne data analysis with Azure Synapse Analytics](/azure/architecture/industries/aerospace/geospatial-processing-analytics)
-

articles/partner-solutions/overview.md

@@ -10,7 +10,7 @@ ms.author: franlanglois
 
 # Azure Native ISV Services overview
 
-Azure Native ISV Services enable you to easily provision, manage, and tightly integrate *independent software vendor* (ISV) software and services on Azure. Azure Native ISV Services is developed and managed by Microsoft and the ISV. Currently, several services are publicly available across these areas: observability, data, networking, and storage. For a list of all our current ISV partner services, see [Extend Azure with Azure Native ISV Services](partners.md).
+Azure Native ISV Services enable you to easily provision, manage, and tightly integrate *independent software vendor (ISV)* software and services on Azure. Azure Native ISV Services is developed and managed by Microsoft and the ISV. Currently, several services are publicly available across these areas: observability, data, networking, and storage. For a list of all our current ISV partner services, see [Extend Azure with Azure Native ISV Services](partners.md).
 
 ## Features of Azure Native ISV Services
 

articles/partner-solutions/qumulo/qumulo-disaster-recovery.md

@@ -72,7 +72,7 @@ Here's the basic workflow for ANQ for disaster recovery:
 
 The solution architecture comprises the following components:
 
-- [Azure Native Qumulo Scalable File Service (ANQ)](https://qumulo.com/azure)
+- [Azure Native Qumulo (ANQ) Scalable File Service](https://qumulo.com/azure)
 - [Qumulo Continuous Replication](https://care.qumulo.com/hc/articles/360018873374-Replication-Continuous-Replication-with-2-11-2-and-above)
 - [Qumulo Snapshots with Replication](https://care.qumulo.com/hc/articles/360037962693-Replication-Snapshot-Policy-Replication)
 - [Azure Virtual Network](/azure/virtual-network/virtual-networks-overview)

articles/partner-solutions/qumulo/qumulo-vendor-neutral-archive.md

@@ -55,7 +55,7 @@ The process flow for Azure Native Qumulo for PACS VNA is depicted here:
 
 The solution architecture comprises the following components:
 
-- [Azure Native Qumulo Scalable File Service (ANQ)](https://qumulo.com/azure) to provide consolidated, cloud-based VNA archive services
+- [Azure Native Qumulo (ANQ) Scalable File Service](https://qumulo.com/azure) to provide consolidated, cloud-based VNA archive services
 - One-way replication enabled between the on-premises Qumulo cluster(s) and the target ANQ cluster on Azure.
 - On-premises PACS application environment(s), configured to export VNA formatted data to the local Qumulo cluster
 - [Azure Virtual Network](/azure/virtual-network/virtual-networks-overview)