fix the block issues

Author: v-lanjli

articles/synapse-analytics/spark/apache-spark-azure-log-analytics.md

@@ -57,12 +57,12 @@ spark.synapse.diagnostic.emitter.LA.secret: <LOG_ANALYTICS_WORKSPACE_KEY>
 #### Option 2: Configure with Azure Key Vault
 
 > [!NOTE]
-> You need to grant read secret permission to the users who will submit Apache Spark applications. For more information, see [Provide access to Key Vault keys, certificates, and secrets with an Azure role-based access control](/azure/key-vault/general/rbac-guide). When you enable this feature in a Synapse pipeline, you need to use **Option 3**. This is necessary to obtain the secret from Azure Key Vault with workspace managed identity.
+> You need to grant read secret permission to the users who submit Apache Spark applications. For more information, see [Provide access to Key Vault keys, certificates, and secrets with an Azure role-based access control](/azure/key-vault/general/rbac-guide). When you enable this feature in a Synapse pipeline, you need to use **Option 3**. This is necessary to obtain the secret from Azure Key Vault with workspace managed identity.
 
 To configure Azure Key Vault to store the workspace key, follow these steps:
 
 1. Create and go to your key vault in the Azure portal.
-1. Grant the right permission to the users or workspace managed identites.
+1. Grant the right permission to the users or workspace managed identities.
 1. On the settings page for the key vault, select **Secrets**.
 1. Select **Generate/Import**.
 1. On the **Create a secret** screen, choose the following values:
@@ -146,7 +146,7 @@ You can create an Apache Spark Configuration to your workspace, and when you cre
    1. Select **New** button to create a new Apache Spark configuration.
    1. **New Apache Spark configuration** page will be opened after you select **New** button.
 
-      :::image type="content" source="./media/apache-spark-azure-log-analytics/create-spark-configuration.png" alt-text="Screenshot that create spark configuration.":::
+      :::image type="content" source="./media/apache-spark-azure-log-analytics/create-spark-configuration.png" alt-text="Screenshot that creates Spark configuration.":::
 
    1. For **Name**, you can enter your preferred and valid name.
    1. For **Description**, you can input some description in it.
@@ -277,7 +277,7 @@ You can follow below steps to create a managed private endpoint connection to Az
 1. Navigate to your AMPLS in Azure portal again, on the **Private Endpoint connections** page, select the connection provisioned and **Approve**.
 
 > [!NOTE]
->  - The AMPLS object has a number of limits you should consider when planning your Private Link setup. See [AMPLS limits](/azure/azure-monitor/logs/private-link-security) for a deeper review of these limits. 
+>  - The AMPLS object has many limits you should consider when planning your Private Link setup. See [AMPLS limits](/azure/azure-monitor/logs/private-link-security) for a deeper review of these limits. 
 >  - Check if you have [right permission](../security/synapse-workspace-access-control-overview.md) to create managed private endpoint.
 
 ## Available configurations
@@ -291,7 +291,7 @@ You can follow below steps to create a managed private endpoint connection to Az
 | `spark.synapse.diagnostic.emitter.<destination>.secret`                        | Optional. The secret (Log Aanalytics key) content.  To find this, in the Azure portal, go to Azure Log Analytics workspace > Agents > Primary key. |
 | `spark.synapse.diagnostic.emitter.<destination>.secret.keyVault`            | Required if `.secret` is not specified. The [Azure Key vault](/azure/key-vault/general/overview) name where the secret (AccessKey or SAS) is stored. |
 | `spark.synapse.diagnostic.emitter.<destination>.secret.keyVault.secretName` | Required if `.secret.keyVault` is specified. The Azure Key vault secret name where the secret is stored. |
-| `spark.synapse.diagnostic.emitter.<destination>.secret.keyVault.linkedService` | Optional. The Azure Key vault linked service name. When enabled in Synapse pipeline, this is necessary to obtain the secret from AKV. (Please make sure MSI has read permission on the AKV). |
+| `spark.synapse.diagnostic.emitter.<destination>.secret.keyVault.linkedService` | Optional. The Azure Key vault linked service name. When enabled in Synapse pipeline, this is necessary to obtain the secret from Azure Key vault. (Make sure the MSI has read access to the Azure Key vault). |
 | `spark.synapse.diagnostic.emitter.<destination>.filter.eventName.match`     | Optional. The comma-separated Log4j logger names, you can specify which logs to collect. For example `SparkListenerApplicationStart,SparkListenerApplicationEnd` |
 | `spark.synapse.diagnostic.emitter.<destination>.filter.loggerName.match`    | Optional. The comma-separated log4j logger names, you can specify which logs to collect. For example: `org.apache.spark.SparkContext,org.example.Logger` |
 | `spark.synapse.diagnostic.emitter.<destination>.filter.metricName.match`    | Optional. The comma-separated spark metric name suffixes, you can specify which metrics to collect. For example:`jvm.heap.used` |

articles/synapse-analytics/spark/how-to-use-certsp-emit-log-to-eventhub.md renamed to articles/synapse-analytics/spark/how-to-use-certificate-with-service-principalp-emit-log-event-hubs.md

@@ -1,20 +1,20 @@
 ---
-title: How to use cert+sp emit log to eventhub
-description: Learn to setting up Azure services, particularly focusing on integrating Azure Synapse with Event Hubs and Key Vault.
+title: How to use certificate and Service Principal emit log to Azure Event Hubs
+description: Learn to setting up Azure services, particularly focusing on integrating Azure Synapse with Azure Event Hubs and Key Vault.
 author: jejiang
 ms.author: jejiang
 ms.reviewer: whhender
 ms.topic: tutorial
 ms.date: 03/24/2025
 ---
 
-# How to use certificate and Service Principal emit log to eventhub
+# How to use certificate and service principal emit log to Azure Event Hubs
 
 ## Prerequisites
 
-- An Azure subscription. If you don't have one, [create a free account](https://azure.microsoft.com/free/) before you begin.
-- [Synapse Analytics workspace](/azure/synapse-analytics/get-started-create-workspace)
-- If you are new to Azure Event Hubs, read through [Event Hubs overview](/azure/event-hubs/event-hubs-about) and [Event Hubs features](/azure/event-hubs/event-hubs-features).
+- An Azure subscription. You can also [create a free account](https://azure.microsoft.com/free/) before you get started.
+- [Synapse Analytics workspace](/azure/synapse-analytics/get-started-create-workspace).
+- [Azure Event Hubs](/azure/event-hubs/event-hubs-about).
 - [Azure Key Vault](/azure/key-vault/general/overview)
 - [App Registration](https://ms.portal.azure.com/#view/Microsoft_AAD_RegisteredApps/ApplicationsListBlade)
 
@@ -28,17 +28,17 @@ ms.date: 03/24/2025
 1. Sign in to the [Azure portal](https://portal.azure.com/) and go to [App registrations](/entra/identity-platform/quickstart-register-app#register-an-application).
 2. Create a new app registration for your Synapse workspace.
 
-     :::image type="content" source="media\how-to-use-certsp-emit-log-to-eventhub\create-a-new-app-registration.png" alt-text="Screenshot showing create a new app registration.":::
+     :::image type="content" source="media\how-to-use-certificate-with-service-principalp-emit-log-event-hubs\create-a-new-app-registration.png" alt-text="Screenshot showing create a new app registration.":::
 
-## Step 2. Generate a Certificate in Key Vault
+## Step 2. Generate a certificate in Key Vault
 
 1. Navigate to Key Vault.
 2. Expand the **Object**, and select the **Certificates**.
 3. Click on **Generate/Import**. 
 
-     :::image type="content" source="media\how-to-use-certsp-emit-log-to-eventhub\generate-a-new-certificate.png" alt-text="Screenshot showing generate a new certificate for app.":::
+     :::image type="content" source="media\how-to-use-certificate-with-service-principalp-emit-log-event-hubs\generate-a-new-certificate.png" alt-text="Screenshot showing generate a new certificate for app.":::
 
-## Step 3. Trust the Certificate in the Application 
+## Step 3. Trust the certificate in the application 
 
 1. Go to the app created in Step 1 -> **Manage** -> **Manifest**. 
 2. Append the certificate details to the manifest file to establish trust. 
@@ -53,27 +53,27 @@ ms.date: 03/24/2025
           ] 
      ```
 
-     :::image type="content" source="media\how-to-use-certsp-emit-log-to-eventhub\trust-the-certificate.png" alt-text="Screenshot showing trust the certificate in the application.":::
+     :::image type="content" source="media\how-to-use-certificate-with-service-principalp-emit-log-event-hubs\trust-the-certificate.png" alt-text="Screenshot showing trust the certificate in the application.":::
 
 ## Step 4. Assign Azure Event Hubs Data Sender Role 
 
-1. In Event Hub, navigate to Access control (IAM).
-2. Assign the app (Service Principal) with the Azure Event Hubs Data Sender role. 
+1. In Azure Event Hubs, navigate to Access control (IAM).
+2. Assign the Azure Event Hubs data sender role to the application (service principal).
 
-     :::image type="content" source="media\how-to-use-certsp-emit-log-to-eventhub\assign-azure-event-hubs-data-sender-role.png" alt-text="Screenshot showing assign azure event hubs data sender role.":::
+     :::image type="content" source="media\how-to-use-certificate-with-service-principalp-emit-log-event-hubs\assign-azure-event-hubs-data-sender-role.png" alt-text="Screenshot showing assign Azure event hubs data sender role.":::
 
-## Step 5. Create a Linked Service in Synapse
+## Step 5. Create a linked service in Synapse
 
-1. In Synapse Analytics workspace, go to **Manage** -> **Linked service**.
-2. Create a new **Linked Service** in Synapse to connect to **Key Vault**. 
+1. In Synapse Analytics workspace, go to **Manage** -> **linked service**.
+2. Create a new **linked Service** in Synapse to connect to **Key Vault**. 
 
-     :::image type="content" source="media\how-to-use-certsp-emit-log-to-eventhub\create-a-linked-service-in-synapse.png" alt-text="Screenshot showing create a linked service in synapse.":::
+     :::image type="content" source="media\how-to-use-certificate-with-service-principalp-emit-log-event-hubs\create-a-linked-service-in-synapse.png" alt-text="Screenshot showing create a linked service in synapse.":::
 
-## Step 6. Assign Reader Role to Linked Service in Key Vault
+## Step 6. Assign reader role to linked service in Key Vault
 
-1. Get the workspace managed identity ID from the linked service. The **managed identity name** and **object ID** for the linked service is under **Edit Linked Service**. 
+1. Get the workspace managed identity ID from the linked service. The **managed identity name** and **object ID** for the linked service is under **Edit linked service**. 
 
-     :::image type="content" source="media\how-to-use-certsp-emit-log-to-eventhub\managed-identity-name-and-object-id.png" alt-text="Screenshot showing managed identity name and object id are in edit linked service.":::
+     :::image type="content" source="media\how-to-use-certificate-with-service-principalp-emit-log-event-hubs\managed-identity-name-and-object-id.png" alt-text="Screenshot showing managed identity name and object ID are in edit linked service.":::
 
 2. In **Key Vault**, assign the linked service a **Reader** role. 
 
@@ -84,10 +84,10 @@ Gather the following values and add to the Apache Spark configuration.
 - **<EMITTER_NAME>**: The name for the emmiter.
 - **<CERTIFICATE_NAME>**: The certificate name that you generated in the key vault.
 - **<LINKED_SERVICE_NAME>**: The Azure Key vault linked service name.
-- **<EVENT_HUB_HOST_NAME>**: The Event Hub host name, you can find it in Event Hubs Namespace -> Overview -> Host name.
-- **<SERVICE_PRINCIPAL_TENANT_ID>**: The service principal tenant id, you can find it in App registrations -> your app name -> Overview -> Directory (tenant) ID
-- **<SERVICE_PRINCIPAL_CLIENT_ID>**: The service principal client id, you can find it in registrations -> your app name -> Overview -> Application(client) ID
-- **<EVENT_HUB_ENTITY_PATH>**: The Event Hub entity path, you can find it in Event Hubs Namespace -> Overview -> Host name.
+- **<EVENT_HUB_HOST_NAME>**: The Azure Event Hubs host name, you can find it in Azure Event Hubs Namespace -> Overview -> Host name.
+- **<SERVICE_PRINCIPAL_TENANT_ID>**: The service principal tenant ID, you can find it in App registrations -> your app name -> Overview -> Directory (tenant) ID
+- **<SERVICE_PRINCIPAL_CLIENT_ID>**: The service principal client ID, you can find it in registrations -> your app name -> Overview -> Application(client) ID
+- **<EVENT_HUB_ENTITY_PATH>**: The Azure Event Hubs entity path, you can find it in Azure Event Hubs Namespace -> Overview -> Host name.
 
 ```
      "spark.synapse.diagnostic.emitters": <EMITTER_NAME>,

articles/synapse-analytics/spark/media/how-to-use-certsp-emit-log-to-eventhub/assign-azure-event-hubs-data-sender-role.png renamed to articles/synapse-analytics/spark/media/how-to-use-certificate-with-service-principalp-emit-log-event-hubs/assign-azure-event-hubs-data-sender-role.png

@@ -817,7 +817,7 @@ items:
       - name: Collect Apache Spark applications logs and metrics with Azure Event Hubs
         href: ./spark/azure-synapse-diagnostic-emitters-azure-eventhub.md
       - name: Collect Apache Spark applications logs and metrics by certificate and service principal
-        href: ./spark/how-to-use-certsp-emit-log-to-eventhub.md
+        href: ./spark/how-to-use-certificate-with-service-principalp-emit-log-event-hubs.md
       - name: Manage Apache Spark configuration
         href: ./spark/apache-spark-azure-create-spark-configuration.md
       - name: Apache Spark Advisor