Merge pull request #278335 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: Taojunshen

articles/azure-monitor/app/live-stream.md

@@ -40,7 +40,7 @@ Live Metrics is currently supported for ASP.NET, ASP.NET Core, Azure Functions,
 
   Using OpenTelemetry (Recommended):
 
-   * [ASP.NET](opentelemetry-enable.md?tabs=net): Live Metrics is enabled by default.
+   * [ASP.NET](opentelemetry-enable.md?tabs=net): Live Metrics is not supported.
    * [ASP.NET Core](opentelemetry-enable.md?tabs=aspnetcore): Live Metrics is enabled by default.
    * [Java](./opentelemetry-enable.md?tabs=java): Live Metrics is enabled by default.
    * [Node.js](opentelemetry-enable.md?tabs=nodejs): Live Metrics is enabled by default.

articles/container-apps/tutorial-dev-services-postgresql.md

@@ -446,7 +446,7 @@ Azure CLI commands and Bicep template fragments are featured in this tutorial. I
 
 ## Create an app to test the service
 
-When you creat the app, you begin by creating a debug app to use the `psql` CLI to connect to the PostgreSQL instance.
+When you create the app, you begin by creating a debug app to use the `psql` CLI to connect to the PostgreSQL instance.
 
 1. Create a `psql` app that binds to the PostgreSQL service.
 

articles/virtual-machines/workloads/oracle/oracle-reference-architecture.md

@@ -106,9 +106,9 @@ The following diagram is a high availability architecture using Oracle Data Guar
 
 :::image type="content" source="./media/oracle-reference-architecture/oracledb_dg_fs_az.png" alt-text="Diagram that shows Oracle database using availability zones with Data Guard Far Sync & Broker - FSFO." lightbox="./media/oracle-reference-architecture/oracledb_dg_fs_az.png":::
 
-In the preceding architecture, there's a Far Sync instance deployed in the same availability zone as the database instance to reduce the latency between the two. In cases where the application is latency sensitive, consider deploying your database and Far Sync instance or instances in a [proximity placement group](../../../virtual-machines/linux/proximity-placement-groups.md).
+In the preceding architecture, there's a Far Sync instance deployed in a different availability zone as the database instance to ensure zero data loss and automatic failover in case of availability zone failure. In cases where the application is latency sensitive, consider deploying your database and Far Sync instance or instances in the same availability zone in a [proximity placement group](../../../virtual-machines/linux/proximity-placement-groups.md).
 
-The following diagram is an architecture that uses Oracle Data Guard FSFO and Far Sync to achieve high availability and disaster recovery:
+The following diagram is an architecture that uses Oracle Data Guard FSFO and Far Sync to achieve high availability and disaster recovery: 
 
 :::image type="content" source="./media/oracle-reference-architecture/oracledb_dg_fs_az_dr.png" alt-text="Diagram that shows Oracle Database using availability zones for disaster recovery with Data Guard Far Sync and Broker - FSFO." lightbox="./media/oracle-reference-architecture/oracledb_dg_fs_az_dr.png":::