Merge pull request #229483 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/chaos-studio/chaos-studio-private-networking.md

@@ -16,7 +16,7 @@ VNet is the fundamental building block for your private network in Azure. VNet e
 
 VNet injection allows a Chaos resource provider to inject containerized workloads into your VNet so that resources without public endpoints can be accessed via a private IP address on the VNet. To configure VNet injection:
 
-1. Register the `Microsoft.ContainerInstance` resource provider with your subscription (if applicable).
+1. Register the `Microsoft.ContainerInstance` and `Microsoft.Relay` resource providers with your subscription (if applicable).
 
     ```bash
     az provider register --namespace 'Microsoft.ContainerInstance' --wait

articles/cloud-shell/embed-cloud-shell.md

@@ -37,13 +37,13 @@ To integrate Cloud Shell's launch button into markdown files by copying the foll
 Regular sized button
 
 ```markdown
-[![Launch Cloud Shell](https://learn.microsoft.com/azure/cloud-shell/media/embed-cloud-shell/launch-cloud-shell-1.png](https://shell.azure.com)
+[![Launch Cloud Shell](https://learn.microsoft.com/azure/cloud-shell/media/embed-cloud-shell/launch-cloud-shell-1.png)](https://shell.azure.com)
 ```
 
 Large sized button
 
 ```markdown
-[![Launch Cloud Shell](https://learn.microsoft.com/azure/cloud-shell/media/embed-cloud-shell/launch-cloud-shell-2.png](https://shell.azure.com)
+[![Launch Cloud Shell](https://learn.microsoft.com/azure/cloud-shell/media/embed-cloud-shell/launch-cloud-shell-2.png)](https://shell.azure.com)
 ```
 
 The location of these image files is subject to change. We recommend that you download the files for

articles/confidential-computing/confidential-vm-faq-amd.yml

@@ -42,15 +42,15 @@ sections:
           Collectively, AMD SEV technologies harden guest protections to deny hypervisor and other host management code access to VM memory and state. 
           Confidential VMs combine AMD SEV-SNP with Azure technologies such as full-disk encryption and [Azure Key Vault Managed HSM](../key-vault/managed-hsm/overview.md). 
           You can encrypt data in use, in transit, and at rest with keys that you control. 
-          With built-in [Azure Attestation](https://azure.microsoft.com/services/azure-attestation/) capabilities, you can independently establish trust in the security health and underlying infrastructure of your confidential VMs.
+          With built-in [Azure Attestation](https://azure.microsoft.com/services/azure-attestation/) capabilities, you can independently establish trust in the security, health and underlying infrastructure of your confidential VMs.
 
       - question: |
           How do Azure confidential VMs (DCasv5/ECasv5) offer better protection against threats originating from both within and outside Azure cloud infrastructure? 
         answer: |
           Azure VMs already offer industry leading security and protection against other tenants and malicious intruders. 
           Azure confidential VMs augment these protections by using hardware-based TEEs (Trusted Execution Environment) which leverage AMD’s SEV-SNP to cryptographically isolate and protect your data confidentiality and integrity even when they are in use. 
-          This means not host admins, or services (including the Azure hypervisor) can directly view or modify the memory or CPU state of your VM. 
-          Moreover, with full attestation capability, full OS disk encryption and hardeware-protected virtual Trusted Platform Modules, confidential VM persistent state is protected such that neither your private keys, nor are the contents of your memory are ever exposed to the hosting environment.
+          This means neither host admins, nor services (including the Azure hypervisor) can directly view or modify the memory or CPU state of your VM. 
+          Moreover, with full attestation capability, full OS disk encryption and hardware-protected virtual Trusted Platform Modules, confidential VM persistent state is protected such that neither your private keys, nor the contents of your memory are ever exposed to the hosting environment.
 
       - question: |
           Are the virtual disks attached to confidential VMs automatically protected?

articles/operator-nexus/howto-baremetal-functions.md

@@ -13,7 +13,7 @@ ms.custom: template-how-to
 
 This article describes how to perform lifecycle management operations on Bare Metal Machines (BMM). These steps should be used for troubleshooting purposes to recover from failures or when taking maintenance actions. The commands to manage the lifecycle of the BMM include:
 
-- Power-off
+- Power off the BMM
 - Start the BMM
 - Make the BMM unschedulable or schedulable
 - Reinstall the BMM image
@@ -23,9 +23,9 @@ This article describes how to perform lifecycle management operations on Bare Me
 1. Install the latest version of the
   [appropriate CLI extensions](./howto-install-cli-extensions.md)
 1. Ensure that the target bare metal machine (server) must have its `poweredState` set to `On` and have its `readyState` set to `True`
-1. Get the Resource group name that you created for `network cloud cluster resource`
+1. Get the Resource group name that you created for `Cluster` resource
 
-## Power-off bare metal machines
+## Power off the BMM
 
 This command will `power-off` the specified `bareMetalMachineName`.
 
@@ -34,7 +34,7 @@ This command will `power-off` the specified `bareMetalMachineName`.
         --resource-group "resourceGroupName"
 ```
 
-## Start bare metal machine
+## Start the BMM
 
 This command will `start` the specified `bareMetalMachineName`.
 

articles/postgresql/flexible-server/quickstart-create-server-bicep.md

@@ -1,5 +1,5 @@
 ---
-title: 'Quickstart: Create an Azure DB for PostgreSQL Flexible Server - Bicep'
+title: 'Quickstart: Create an Azure Database for PostgreSQL Flexible Server - Bicep'
 description: In this Quickstart, learn how to create an Azure Database for PostgreSQL Flexible server using Bicep.
 author: mumian
 ms.service: postgresql

articles/storage/blobs/blob-inventory.md

@@ -22,7 +22,7 @@ The following list describes features and capabilities that are available in the
 
 - **Inventory reports for blobs and containers**
 
-  You can generate inventory reports for blobs and containers. A report for blobs can contain base blobs, snapshots, content length, blob versions and their associated properties such as creation time, last modified time. A report for containers describes containers and their associated properties such as immutability policy status, legal hold status. 
+  You can generate inventory reports for blobs and containers. A report for blobs can contain base blobs, snapshots, content length, blob versions and their associated properties such as creation time, last modified time. Empty containers aren’t listed in the Blob Inventory report. A report for containers describes containers and their associated properties such as immutability policy status, legal hold status. 
 
 - **Custom Schema**