Acrolinx fixes

DeCohen · DeCohen · commit 5a4104ae4790 · 2025-01-20T16:26:11.000+02:00
diff --git a/CloudAppSecurityDocs/api-tokens-legacy.md b/CloudAppSecurityDocs/api-tokens-legacy.md
@@ -8,15 +8,15 @@ ms.topic: reference
 
 
 
-In order to access the Defender for Cloud Apps API, you have to create an API token and use it in your software to connect to the API. This token will be included in the header when Defender for Cloud Apps makes API requests.
+In order to access the Defender for Cloud Apps API, you have to create an API token and use it in your software to connect to the API. This token is included in the header when Defender for Cloud Apps makes API requests.
 
 The API tokens tab enables you to help you manage all the API tokens of your tenant.
 
 ## Generate a token
 
 1. In the Microsoft Defender Portal, select **Settings**. Then choose **Cloud Apps**. Under **System**, select **API tokens**.
 
-1. Select the **Add token** and provide a name to identify the token in the future, and select **Generate**.
+1. Select **Add token** and provide a name to identify the token in the future, and select **Generate**.
 
     ![Defender for Cloud Apps generates API token.](media/api-token-gen.png)
 
@@ -46,7 +46,7 @@ After a token is revoked, it's removed from the table, and the software that was
 
 > [!NOTE]
 >
-> - SIEM connectors and log collectors also use API tokens. These tokens should be managed from the log collectors and SIEM agent sections and do not appear in this table.
-> - Deprovisioned users API tokens are retained in Defender for Cloud Apps but cannot be used. Any attempt to use them will result in a permission denied response. However, we recommend that such tokens are revoked on the **API tokens** page.
+> - SIEM connectors and log collectors also use API tokens. These tokens should be managed from the log collectors and SIEM agent sections and don't appear in this table.
+> - Deprovisioned users API tokens are retained in Defender for Cloud Apps but can't be used. Any attempt to use them will result in a permission denied response. However, we recommend that such tokens are revoked on the **API tokens** page.
 
 [!INCLUDE [Open support ticket](includes/support.md)]
diff --git a/CloudAppSecurityDocs/azip-integration.md b/CloudAppSecurityDocs/azip-integration.md
@@ -6,7 +6,7 @@ ms.topic: how-to
 ---
 # Integrate with Microsoft Purview for information protection
 
-Microsoft Defender for Cloud Apps lets you automatically apply sensitivity labels from Microsoft Purview. These labels are applied to files as a file policy governance action, and depending on the label configuration, can apply encryption for additional protection. You can also investigate files by filtering for the applied sensitivity label within the Defender for Cloud Apps. Using labels enables greater visibility and control of your sensitive data in the cloud. Integrating Microsoft Purview with Defender for Cloud Apps is as easy as selecting a single checkbox.
+Microsoft Defender for Cloud Apps lets you automatically apply sensitivity labels from Microsoft Purview. These labels are applied to files as a file policy governance action, and depending on the label configuration, can apply encryption for additional protection. You can also investigate files by filtering for the applied sensitivity label within Defender for Cloud Apps. Using labels enables greater visibility and control of your sensitive data in the cloud. Integrating Microsoft Purview with Defender for Cloud Apps is as easy as selecting a single checkbox.
 
 By integrating Microsoft Purview into Defender for Cloud Apps, you can use the full power of both services and secure files in your cloud, including:
 
diff --git a/CloudAppSecurityDocs/ems-cloud-app-security-govt-service-byok-troubleshoot.md b/CloudAppSecurityDocs/ems-cloud-app-security-govt-service-byok-troubleshoot.md
@@ -11,19 +11,19 @@ ms.topic: conceptual
 This article provides a list of problems that can prevent Defender for Cloud Apps from accessing your Azure Key Vault key used to encrypt collected data at rest.
 
 > [!IMPORTANT]
-> If there is a problem accessing your Azure Key Vault key, Defender for Cloud Apps will fail to encrypt your data and your tenant will be lock down within an hour. When your tenant is locked down, all access to it will be blocked until the cause has been resolved. Once your key is accessible again, full access to your tenant will be restored
+> If there's a problem accessing your Azure Key Vault key, Defender for Cloud Apps will fail to encrypt your data, and your tenant will be locked down within an hour. When your tenant is locked down, all access to it will be blocked until the cause has been resolved. Once your key is accessible again, full access to your tenant will be restored
 
 ## Troubleshooting
 
 The following table lists the possible scenarios that can cause data encryption to fail and the actions you can take to resolve them:
 
 | Scenario | Actions |
 | --- | --- |
-| <a name="missing-kv-key-permissions"></a>**Missing Key Vault or key permissions** | In the selected Key Vault, under access policy, make sure that the following key permissions are selected:<br />Under **Key management operations**<br />- List<br />Under **Cryptographic operations**<br />- Wrap key<br />- Unwrap key<br /><br />For the selected key, make sure you are using an RSA encryption and that the following operations are permitted:<br />- Wrap key<br />- Unwrap key<br /> |
+| <a name="missing-kv-key-permissions"></a>**Missing Key Vault or key permissions** | In the selected Key Vault, under access policy, make sure that the following key permissions are selected:<br />Under **Key management operations**<br />- List<br />Under **Cryptographic operations**<br />- Wrap key<br />- Unwrap key<br /><br />For the selected key, make sure you're using an RSA encryption and that the following operations are permitted:<br />- Wrap key<br />- Unwrap key<br /> |
 | <a name="firewall-block"></a>**Azure Key Vault firewall blocking access to key** | In the selected Key Vault, make sure that the firewall is configured with the following IP addresses:<br />- 13.66.200.132<br />- 23.100.71.251<br />- 40.78.82.214<br />- 51.105.4.145<br />- 52.166.166.111 |
 | <a name="key-not-enabled"></a>**Encryption key is not enabled** | In the selected key's settings, make sure that the key is enabled.<br />![Screenshot showing key enable option.](media/cloud-app-security-byok/byok-kv-key-enabled.PNG) |
 | <a name="key-not-active"></a>**Encryption key is not active** | In the selected key's settings, make sure that the activation date and time is prior to the current date and time.<br />![Screenshot showing key activation date.](media/cloud-app-security-byok/byok-kv-key-activation-date.PNG) |
-| <a name="key-expired"></a>**Encryption key has expired** | In the selected key's settings, make sure that the expiration date and time has not passed.<br />![Screenshot showing key expiration date.](media/cloud-app-security-byok/byok-kv-key-expiration-date.PNG) |
+| <a name="key-expired"></a>**Encryption key has expired** | In the selected key's settings, make sure that the expiration date and time hasn't passed.<br />![Screenshot showing key expiration date.](media/cloud-app-security-byok/byok-kv-key-expiration-date.PNG) |
 | <a name="key-not-found"></a>**Encryption key not found or deleted** | Verify that the selected key exists in your Key Vault. If key was deleted, recover and enable it again. If the key was moved to another Key Vault, move it back to the selected Key Vault. |
 
 If you run into any problems, we're here to help. To get assistance or support for your product issue, please [open a support ticket](./support-and-ts.md).
