Merge pull request #79609 from KingdomOfEnds/dt-accessibility

replaced click

Author: PRMerger15

articles/digital-twins/how-to-configure-monitoring.md

@@ -63,11 +63,11 @@ Examples of diagnostic logging include:
 To enable diagnostic logs for an instance:
 
 1. Bring up the resource in Azure portal.
-1. Click **Diagnostic settings**:
+1. Select **Diagnostic settings**:
 
     [![Diagnostic settings one](media/how-to-configure-monitoring/diagnostic-settings-one.png)](media/how-to-configure-monitoring/diagnostic-settings-one.png#lightbox)
 
-1. Click **Turn on diagnostics** to collect data (if not previously enabled).
+1. Select **Turn on diagnostics** to collect data (if not previously enabled).
 1. Fill in the requested fields and select how and where data will be saved:
 
     [![Diagnostic settings two](media/how-to-configure-monitoring/diagnostic-settings-two.png)](media/how-to-configure-monitoring/diagnostic-settings-two.png#lightbox)
@@ -96,7 +96,7 @@ Full log querying is provided through [Azure Monitor logs](../azure-monitor/log-
 
     [![Log analytics](media/how-to-configure-monitoring/log-analytics.png)](media/how-to-configure-monitoring/log-analytics.png#lightbox)
 
-1. If you don't already have a **Log Analytics workspace** instance, you can create a workspace by clicking the **Add** button:
+1. If you don't already have a **Log Analytics workspace** instance, you can create a workspace by selecting the **Add** button:
 
     [![Create OMS](media/how-to-configure-monitoring/log-analytics-oms.png)](media/how-to-configure-monitoring/log-analytics-oms.png#lightbox)
 
@@ -109,7 +109,7 @@ For more information about powerful query operations, see [getting started with
 > [!NOTE]
 > You may experience a 5 minute delay when sending events to **Log Analytics workspace** for the first time.
 
-Azure Monitor logs also provide powerful error and alert notification services, which can be viewed by clicking **Diagnose and solve problems**:
+Azure Monitor logs also provide powerful error and alert notification services, which can be viewed by selecting **Diagnose and solve problems**:
 
    [![Alert and error notifications](media/how-to-configure-monitoring/log-analytics-notifications.png)](media/how-to-configure-monitoring/log-analytics-notifications.png#lightbox)
 

articles/digital-twins/how-to-configure-postman.md

@@ -36,7 +36,7 @@ Configure your Azure Active Directory app to use the OAuth 2.0 implicit grant fl
 
     [![Azure Active Directory app registrations add api](../../includes/media/digital-twins-permissions/aad-app-req-permissions.png)](../../includes/media/digital-twins-permissions/aad-app-req-permissions.png#lightbox)
 
-1. Click **Manifest** to open the application manifest for your app. Set *oauth2AllowImplicitFlow* to `true`.
+1. Select **Manifest** to open the application manifest for your app. Set *oauth2AllowImplicitFlow* to `true`.
 
     [![Azure Active Directory implicit flow](media/how-to-configure-postman/implicit-flow.png)](media/how-to-configure-postman/implicit-flow.png#lightbox)
 
@@ -106,7 +106,7 @@ After completing the previous steps, configure Postman to make an authenticated
    > * You do not need to specify those headers for each part.
    > * You must select `multipart/mixed` or another appropriate  **Content-Type** for the entire request.
 
-1. Lastly, click **Send** to submit your multipart HTTP POST request.
+1. Lastly, select **Send** to submit your multipart HTTP POST request.
 
 ## Next steps
 

articles/digital-twins/how-to-use-swagger.md

@@ -107,17 +107,17 @@ To learn more about interactively testing requests protected by OAuth 2.0, see t
 
     ![Azure AD app registrations add api](../../includes/media/digital-twins-permissions/aad-app-req-permissions.png)
 
-4. Configure the application manifest to allow OAuth 2.0 implicit flow. Click **Manifest** to open the application manifest for your app. Set *oauth2AllowImplicitFlow* to `true`.
+4. Configure the application manifest to allow OAuth 2.0 implicit flow. Select **Manifest** to open the application manifest for your app. Set *oauth2AllowImplicitFlow* to `true`.
 
     ![Azure AD implicit flow](../../includes/media/digital-twins-permissions/aad-app-allow-implicit-flow.png)
 
 5. Copy the ID of your Azure AD app.
 
 After completing the Azure Active Directory registration:
 
-6. Click the **Authorize** button on your swagger page.
+6. Select the **Authorize** button on your swagger page.
 
-    [![Click the Swagger authorize button](media/how-to-use-swagger/swagger-select-authorize-btn.png)](media/how-to-use-swagger/swagger-select-authorize-btn.png#lightbox)
+    [![Select the Swagger authorize button](media/how-to-use-swagger/swagger-select-authorize-btn.png)](media/how-to-use-swagger/swagger-select-authorize-btn.png#lightbox)
 
 7. Paste the application ID into the **client_id** field.