Improve security documentation clarity (#22187)

hyperlint-ai[bot] · dcpena · daisyfaithauma · commit 8aa3d1c90765 · 2025-05-08T11:47:59.000+03:00
* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Hyperlint Automation Fix

* Undo a hyperlint commit

* fixed wording

---------

Co-authored-by: hyperlint-ai[bot] &lt;154288675+hyperlint-ai[bot]@users.noreply.github.com&gt;
Co-authored-by: Denise Peña &lt;75506267+dcpena@users.noreply.github.com&gt;
diff --git a/src/content/docs/fundamentals/security/recovering-from-hacked-site.mdx b/src/content/docs/fundamentals/security/recovering-from-hacked-site.mdx
@@ -14,7 +14,7 @@ To recover from an attack, reach out to your hosting provider to request:
 * Details about the hack, including how they believe the site was hacked.
 * That your hosting provider remove any malicious content placed on your website.
 
-Once the hack has been resolved, you should resolve site warnings in [Google Webmaster Tools](https://www.google.com/webmasters/tools) and resubmit your site for Google’s review.
+Once the hack has been resolved, you should resolve site warnings in [Google Webmaster Tools](https://www.google.com/webmasters/tools) and resubmit your site for Google's review.
 
 ***
 
diff --git a/src/content/docs/fundamentals/security/under-ddos-attack.mdx b/src/content/docs/fundamentals/security/under-ddos-attack.mdx
@@ -15,7 +15,7 @@ import { Render } from "~/components"
 Common signs that you are under DDoS attack include:
 
 * Your site is offline or slow to respond to requests.
-* There are unexpected spikes in the graph of **Requests Through Cloudflare** or **Bandwidth** in your Cloudflare **Analytics** app.
+* Unexpected spikes appear in the graph of **Requests Through Cloudflare** or **Bandwidth** in your Cloudflare **Analytics** app.
 * There are strange requests in your origin web server logs that do not match normal visitor behavior.
 
 :::note
diff --git a/src/content/docs/fundamentals/setup/account/account-security/login-and-account-issues.mdx b/src/content/docs/fundamentals/setup/account/account-security/login-and-account-issues.mdx
@@ -4,7 +4,7 @@ pcx_content_type: troubleshooting
 
 ---
 
-## Forgot your email?
+## Forgot your email
 
 ### Enterprise plans
 
@@ -29,7 +29,7 @@ Cloudflare requires these steps to prevent account hijacking.
 
 ***
 
-## Forgot your password?
+## Forgot your password
 
 If you forget your account password:
 
diff --git a/src/content/docs/fundamentals/setup/account/account-security/scim-setup.mdx b/src/content/docs/fundamentals/setup/account/account-security/scim-setup.mdx
@@ -64,7 +64,7 @@ To start, you will need to collect a couple of pieces of data from Cloudflare an
 
 ## Provision with Okta
 
-### Set up your Okta SCIM application.
+### Set up your Okta SCIM application
 
 1. In the Okta dashboard, go to **Applications** > **Applications**.
 2. Select **Browse App Catalog**.
@@ -102,7 +102,7 @@ This will provision all of the users in the group(s) affected to your Cloudflare
 
 ### Configure user permissions
 
-There are two options for managing user permissions:
+Two options exist for managing user permissions:
 
 * Manage your user permissions on a per-user basis in the Cloudflare dashboard, API, or using Terraform.
 * Map your IdP groups to a Cloudflare built-in [Role](/fundamentals/setup/manage-members/roles/). Groups may only be linked to one role.
@@ -130,7 +130,7 @@ Adding any users to these groups will grant them the role. Removing the users fr
 
 1. Go to your Microsoft Entra ID instance and select **Enterprise Applications**.
 2. Select **Create your own application** and name your application.
-3. Select **Integrate any other application you don’t find in the gallery (Non-gallery)**.
+3. Select **Integrate any other application you don't find in the gallery (Non-gallery)**.
 4. Select **Create**.
 
 ### Provision the Microsoft Entra ID Enterprise application
@@ -170,4 +170,4 @@ Expectations for user lifecycle management with SCIM:
 | User is removed from account as member         | Unassign the user from the SCIM application.                                                                                                                    |
 | Add role to user                               | Add the user to a group in the IdP which is pushed via SCIM. They must also be assigned to the SCIM application and exist as an account member.                 |
 | Remove role from user                          | Remove the user from the corresponding group in the IdP.                                                                                                        |
-| Retain user in account but with no permissions | Remove the user from all role groups but leave them assigned to the SCIM application. They will be an account member with only the role Minimal Account Access. |
+| Retain user in account but with no permissions | Remove the user from all role groups but leave them assigned to the SCIM application. They will be an account member with only the role Minimal Account Access. |
diff --git a/src/content/docs/fundamentals/setup/accounts-and-zones.mdx b/src/content/docs/fundamentals/setup/accounts-and-zones.mdx
@@ -48,7 +48,7 @@ To access your profile, select the user icon and then **My Profile** from any pa
 
 An account refers to an organization account. Accounts contain one or more users and can contain one or more zones. A user can be part of one or more accounts.
 
-There are also several account-level products - such as [Workers](/workers/), [Pages](/pages/), [Security Center](/security-center/), and [Bulk redirects](/rules/url-forwarding/bulk-redirects/) - that can affect some or all zones contained within that account.
+Several account-level products - such as [Workers](/workers/), [Pages](/pages/), [Security Center](/security-center/), and [Bulk redirects](/rules/url-forwarding/bulk-redirects/) - can affect some or all zones contained within that account.
 
 After you [log in](https://dash.cloudflare.com) and select an account - but before you select a zone - the sidebar will list account-level products.
 
diff --git a/src/content/docs/fundamentals/setup/find-account-and-zone-ids.mdx b/src/content/docs/fundamentals/setup/find-account-and-zone-ids.mdx
@@ -42,7 +42,7 @@ You can also find your account ID from the **Workers & Pages** section of your a
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
 2. Select your account.
-3. Go to **Workers & Pages**. The **Account details** section contains your **Account ID**. 
+3. Go to **Workers & Pages**. The **Account details** section contains your **Account ID**.
 4. To copy the Account ID, select **Click to copy**.
 
 ![Screenshot of the Workers & Pages Overview page with the account ID section highlighted](~/assets/images/fundamentals/get-started/workers-account-id.png)
diff --git a/src/content/docs/fundamentals/setup/interact-with-cloudflare.mdx b/src/content/docs/fundamentals/setup/interact-with-cloudflare.mdx
@@ -22,7 +22,7 @@ For those who prefer to interact with Cloudflare programmatically, you can use s
 | Resource                                                                               | Docs                                                                 | Description                                                                    |
 | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
 | [Cloudflare API](/fundamentals/api/)                                                   | [API docs](/api/)                                                    | RESTful API based on HTTPS requests and JSON responses.                        |
-| [Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) | [Terraform docs](/terraform/)                                        | Configure Cloudflare using HashiCorp’s Infrastructure as Code tool, Terraform. |
+| [Terraform](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) | [Terraform docs](/terraform/)                                        | Configure Cloudflare using HashiCorp's Infrastructure as Code tool, Terraform. |
 | [cloudflare-go](https://github.com/cloudflare/cloudflare-go)                           | [README](https://github.com/cloudflare/cloudflare-go#readme)         | The official Go library for the Cloudflare API.                                |
 | [cloudflare-typescript](https://github.com/cloudflare/cloudflare-typescript)           | [README](https://github.com/cloudflare/cloudflare-typescript#readme) | The official TypeScript library for the Cloudflare API.                        |
 | [cloudflare-python](https://github.com/cloudflare/cloudflare-python)                   | [README](https://github.com/cloudflare/cloudflare-python#readme)     | The official Python library for the Cloudflare API.                            |
diff --git a/src/content/docs/fundamentals/setup/manage-domains/pause-cloudflare.mdx b/src/content/docs/fundamentals/setup/manage-domains/pause-cloudflare.mdx
@@ -10,7 +10,7 @@ To troubleshoot your site, you can pause Cloudflare globally. This will send tra
 
 2. Within **Overview**, choose **Advanced Actions** > **Pause Cloudflare on Site**.
 
-Pausing Cloudflare takes five minutes or less to complete. This is preferable to [changing nameservers](/dns/zone-setups/full-setup/setup/), which can cause propagation delays of several hours.
+The process of pausing Cloudflare takes five minutes or less. This approach is preferable to [changing nameservers](/dns/zone-setups/full-setup/setup/), which can cause propagation delays of several hours.
 
 ***
 
diff --git a/src/content/docs/fundamentals/setup/manage-domains/remove-domain.mdx b/src/content/docs/fundamentals/setup/manage-domains/remove-domain.mdx
@@ -18,7 +18,7 @@ If you have an Enterprise plan, you need to [change the zone plan](/fundamentals
 If you need to re-add the domain in a different account, make sure the current settings have been saved. For example, you may [Import and export DNS records](/dns/manage-dns-records/how-to/import-and-export/).
 
 :::note
-If you have just added a domain and haven't configured its plan yet, the domain is in the `Initializing (Setup)` status and cannot be deleted.
+If you have just added a domain and have not configured its plan yet, the domain is in the `Initializing (Setup)` status and cannot be deleted.
 At this step you'll need to select a plan for this domain: the status will then change to `Pending` and you can then delete the domain.
 Please also note that domains in the `Initializing (Setup)` or `Pending` statuses will [automatically be deleted after 28 days](/dns/zone-setups/reference/domain-status/#initializing-setup) if they do not activate.
 :::
