diff --git a/src/content/partials/analytics/network-analytics-requirements.mdx b/src/content/partials/analytics/network-analytics-requirements.mdx index a6395833c9cbf5d..9bf0eea25f8633e 100644 --- a/src/content/partials/analytics/network-analytics-requirements.mdx +++ b/src/content/partials/analytics/network-analytics-requirements.mdx @@ -9,5 +9,5 @@ Network Analytics requires the following: * A Cloudflare Enterprise plan. * Cloudflare Magic Transit or Spectrum. -* Cloudflare Magic WAN. +* Cloudflare Magic WAN. ::: diff --git a/src/content/partials/api-shield/label-methodology.mdx b/src/content/partials/api-shield/label-methodology.mdx index d4fca4a2f537769..72400e85c006187 100644 --- a/src/content/partials/api-shield/label-methodology.mdx +++ b/src/content/partials/api-shield/label-methodology.mdx @@ -4,6 +4,6 @@ --- | Description | 2xx response codes | 4xx, 5xx response codes | -| --- | --- | --- | +| --- | --- | --- | | If all requests are missing authentication, Cloudflare will apply the label: | `cf-missing-auth` | Without successful responses, no label will be added. | | If only some requests are missing authentication, Cloudflare will apply the label: | `cf-mixed-auth` | Without successful responses, no label will be added. | diff --git a/src/content/partials/api-shield/mtls-api-shield-support.mdx b/src/content/partials/api-shield/mtls-api-shield-support.mdx index 6981e70f90a3629..0224d99943797f8 100644 --- a/src/content/partials/api-shield/mtls-api-shield-support.mdx +++ b/src/content/partials/api-shield/mtls-api-shield-support.mdx @@ -5,5 +5,5 @@ :::note -While API Shield is not required to use mTLS, many teams may use mTLS to protect their APIs. +While API Shield is not required to use mTLS, many teams may use mTLS to protect their APIs. ::: diff --git a/src/content/partials/api-shield/routing-path-variables.mdx b/src/content/partials/api-shield/routing-path-variables.mdx index b53758d831cb34b..0937c2041b7569d 100644 --- a/src/content/partials/api-shield/routing-path-variables.mdx +++ b/src/content/partials/api-shield/routing-path-variables.mdx @@ -5,5 +5,5 @@ :::note -You can reorder path variables if they are present. For example, you can route `/api/{var1}/users/{var2}` to `/{var2}/users/{var1}`. Segments of the path that are not variables may be added or omitted entirely. +You can reorder path variables if they are present. For example, you can route `/api/{var1}/users/{var2}` to `/{var2}/users/{var1}`. Segments of the path that are not variables may be added or omitted entirely. ::: diff --git a/src/content/partials/api-shield/set-up-session-identifiers.mdx b/src/content/partials/api-shield/set-up-session-identifiers.mdx index 9d20a142431f1e1..05484de121ff969 100644 --- a/src/content/partials/api-shield/set-up-session-identifiers.mdx +++ b/src/content/partials/api-shield/set-up-session-identifiers.mdx @@ -12,7 +12,7 @@ :::note The session identifier cookie must comply with RFC 6265. Otherwise, it will be rejected. -If you are using a JWT claim, choose the [Token Configuration](/api-shield/security/jwt-validation/configure/#token-configurations) that will verify the JWT. Token Configurations are required to use JWT claims as session identifiers. Refer to [JWT Validation](/api-shield/security/jwt-validation/) for more information. +If you are using a JWT claim, choose the [Token Configuration](/api-shield/security/jwt-validation/configure/#token-configurations) that will verify the JWT. Token Configurations are required to use JWT claims as session identifiers. Refer to [JWT Validation](/api-shield/security/jwt-validation/) for more information. ::: 6. Enter the name of the session identifier. diff --git a/src/content/partials/bots/ai-bots-definition.mdx b/src/content/partials/bots/ai-bots-definition.mdx index cc5b0f7eca0184b..cf89095a5f5c1b1 100644 --- a/src/content/partials/bots/ai-bots-definition.mdx +++ b/src/content/partials/bots/ai-bots-definition.mdx @@ -3,7 +3,7 @@ --- -You can block artificial intelligence (AI) bots, crawlers, and scrapers from scraping your website content and training large language models (LLM) to recreate it without your permission. +You can block artificial intelligence (AI) bots, crawlers, and scrapers from scraping your website content and training large language models (LLM) to recreate it without your permission. When you enable this feature, all verified bots that are classified as AI Search, AI Assistant, AI Crawler, or an Archiver, as well as a number of unverified bots that fall into the [verified bot categories](/bots/reference/verified-bot-categories/) are blocked. It does not block verified bots that fall into the Search Engine categories. @@ -19,11 +19,11 @@ When you enable this feature via a pre-configured managed rule, Cloudflare can d The rule to block AI bots takes precedence over all other Super Bot Fight Mode rules. For example, if you have enabled **Block AI bots** and **Allow verified bots**, verified AI bots will also be blocked even if you allow other verified bots on your website or application. -For Bot Management customers, if you have set a rule to serve managed challenges to definitely automated bots, AI bots will also be challenged because custom rules run in a phase before Super Bot Fight Mode, which is the phase when the rule to block AI bots runs. +For Bot Management customers, if you have set a rule to serve managed challenges to definitely automated bots, AI bots will also be challenged because custom rules run in a phase before Super Bot Fight Mode, which is the phase when the rule to block AI bots runs. -This behavior remains the same if the setting for verified, definitely automated, and likely bots is set to `block` or `allow`. If you have an action to `allow` for these rules, the request is not matched to any rule and proceeds to the next ruleset phase. Similarly, if the action is set to `block`, they will be blocked in the earlier phase and do not move on to match the AI rule at all. However, when the action is `challenge`, the request matches a rule and therefore will not be matched to any rules after. +This behavior remains the same if the setting for verified, definitely automated, and likely bots is set to `block` or `allow`. If you have an action to `allow` for these rules, the request is not matched to any rule and proceeds to the next ruleset phase. Similarly, if the action is set to `block`, they will be blocked in the earlier phase and do not move on to match the AI rule at all. However, when the action is `challenge`, the request matches a rule and therefore will not be matched to any rules after. -For self-serve non-Bot Management customers, all rules for verified, definitely automated, and likely bots run in the phase following the AI bots rule. +For self-serve non-Bot Management customers, all rules for verified, definitely automated, and likely bots run in the phase following the AI bots rule. ```mermaid --- diff --git a/src/content/partials/bots/bfm-change-notice.mdx b/src/content/partials/bots/bfm-change-notice.mdx index 94a65d85cbb05ac..d7474bab9acd502 100644 --- a/src/content/partials/bots/bfm-change-notice.mdx +++ b/src/content/partials/bots/bfm-change-notice.mdx @@ -5,5 +5,5 @@ :::caution[Change notice for Super Bot Fight Mode rulesets] -Updating Super Bot Fight Mode rules via the Rulesets API is no longer supported and may cause unexpected behavior if you do so. +Updating Super Bot Fight Mode rules via the Rulesets API is no longer supported and may cause unexpected behavior if you do so. ::: diff --git a/src/content/partials/bots/block-ai-bots-enable.mdx b/src/content/partials/bots/block-ai-bots-enable.mdx index 32ce77677eae3ea..862c28d5eb7e940 100644 --- a/src/content/partials/bots/block-ai-bots-enable.mdx +++ b/src/content/partials/bots/block-ai-bots-enable.mdx @@ -5,7 +5,7 @@ inputParameters: param1 import { Markdown } from "~/components" -To block [AI bots](/bots/concepts/bot/#ai-bots): +To block [AI bots](/bots/concepts/bot/#ai-bots): 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain. 2. Go to **Security** > **Bots**. diff --git a/src/content/partials/bots/cf-clearance-cookie.mdx b/src/content/partials/bots/cf-clearance-cookie.mdx index 17c9d3a2ee582d7..6eb65a573c38dc1 100644 --- a/src/content/partials/bots/cf-clearance-cookie.mdx +++ b/src/content/partials/bots/cf-clearance-cookie.mdx @@ -5,7 +5,7 @@ :::note -[JavaScript detections](/bots/reference/javascript-detections/) are stored in the `cf_clearance` cookie. +[JavaScript detections](/bots/reference/javascript-detections/) are stored in the `cf_clearance` cookie. The `cf_clearance` cookie cannot exceed the maximum size of 4096 bytes. ::: \ No newline at end of file diff --git a/src/content/partials/bots/corporate_proxy.mdx b/src/content/partials/bots/corporate_proxy.mdx index 880f7ce5c6c37bf..5cd2e6bb8faa984 100644 --- a/src/content/partials/bots/corporate_proxy.mdx +++ b/src/content/partials/bots/corporate_proxy.mdx @@ -8,8 +8,8 @@ The Bot Management Corporate Proxy field contains identified cloud-based corpora You can access the Corporate Proxy field in [custom rules](/waf/custom-rules/), [rate limiting rules](/waf/rate-limiting-rules/), or [Workers](/workers/) to provide different security rules for traffic from these sources. You can also exempt them from rules using Bot Management scores. ```txt title="Example" -not cf.bot_management.verified_bot -and not cf.bot_management.static_resource +not cf.bot_management.verified_bot +and not cf.bot_management.static_resource and not cf.bot_management.corporate_proxy and cf.bot_management.score lt 30 ``` diff --git a/src/content/partials/bots/disable-cf-bm-cookie.mdx b/src/content/partials/bots/disable-cf-bm-cookie.mdx index 8a81bb83eb52118..7d1ab8cf6e25b89 100644 --- a/src/content/partials/bots/disable-cf-bm-cookie.mdx +++ b/src/content/partials/bots/disable-cf-bm-cookie.mdx @@ -7,5 +7,5 @@ You can begin the process of disabling the `__cf_bm` cookie [via the API](/api/r :::note -The `__cf_bm` cookie cannot be disabled if you have Behavioral Analysis enabled. +The `__cf_bm` cookie cannot be disabled if you have Behavioral Analysis enabled. ::: diff --git a/src/content/partials/bots/get-started-pro-biz-steps.mdx b/src/content/partials/bots/get-started-pro-biz-steps.mdx index 483b49b690371bd..93627eb769bf5bd 100644 --- a/src/content/partials/bots/get-started-pro-biz-steps.mdx +++ b/src/content/partials/bots/get-started-pro-biz-steps.mdx @@ -15,5 +15,5 @@ To start using Super Bot Fight Mode: :::caution[Warning] -If your organization also uses [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/), keep **Definitely Automated** set to **Allow**. Otherwise, tunnels might fail with a `websocket: bad handshake` error. +If your organization also uses [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/), keep **Definitely Automated** set to **Allow**. Otherwise, tunnels might fail with a `websocket: bad handshake` error. ::: diff --git a/src/content/partials/bots/sbfm-upgrade.mdx b/src/content/partials/bots/sbfm-upgrade.mdx index d866c0660168d21..f7c6734d2837f2b 100644 --- a/src/content/partials/bots/sbfm-upgrade.mdx +++ b/src/content/partials/bots/sbfm-upgrade.mdx @@ -4,7 +4,7 @@ --- :::note -If you are upgrading from Bot Fight Mode to Super Bot Fight Mode, you must disable Bot Fight Mode in your Bot settings. +If you are upgrading from Bot Fight Mode to Super Bot Fight Mode, you must disable Bot Fight Mode in your Bot settings. -To turn off Bot Fight Mode, go to **Security** > **Bots** and select **Configure Super Bot Fight Mode**. +To turn off Bot Fight Mode, go to **Security** > **Bots** and select **Configure Super Bot Fight Mode**. ::: \ No newline at end of file diff --git a/src/content/partials/cloudflare-one/access/bookmarks.mdx b/src/content/partials/cloudflare-one/access/bookmarks.mdx index a072e24083ea929..bafc089954328a5 100644 --- a/src/content/partials/cloudflare-one/access/bookmarks.mdx +++ b/src/content/partials/cloudflare-one/access/bookmarks.mdx @@ -21,7 +21,7 @@ Links to applications not protected by Access can be added as bookmarks. To add :::note - If you are having issues specifying a custom logo, check that the image is served from an HTTPS endpoint. For example, `http://www.example.com/upload/logo.png` will not work. However, `https://www.example.com/upload/logo.png` will. + If you are having issues specifying a custom logo, check that the image is served from an HTTPS endpoint. For example, `http://www.example.com/upload/logo.png` will not work. However, `https://www.example.com/upload/logo.png` will. ::: 7. Select **Add application** to save and exit. diff --git a/src/content/partials/cloudflare-one/email-security/detect-phish.mdx b/src/content/partials/cloudflare-one/email-security/detect-phish.mdx index ce4b0a71ebe1c9e..ec9f1d28d2bd8a5 100644 --- a/src/content/partials/cloudflare-one/email-security/detect-phish.mdx +++ b/src/content/partials/cloudflare-one/email-security/detect-phish.mdx @@ -128,7 +128,7 @@ These small pattern assessments are dynamic in nature and — in many cases — ### Mobile phishing -- **Example**: Remote employee getting phished while outside the corporate network. +- **Example**: Remote employee getting phished while outside the corporate network. - **Detections applied**: Employee email protection and web and DNS services enforcement in remote users (typically through an MDM integration or an always-on VPN solution). ### Network phishing diff --git a/src/content/partials/cloudflare-one/gateway/disable-udp.mdx b/src/content/partials/cloudflare-one/gateway/disable-udp.mdx index 3c401ad6b8d9fb5..d2d8afbdcb359e0 100644 --- a/src/content/partials/cloudflare-one/gateway/disable-udp.mdx +++ b/src/content/partials/cloudflare-one/gateway/disable-udp.mdx @@ -11,5 +11,5 @@ DLS does not support UDP traffic with Cloudflare Secure Web Gateway. To prevent 2. Under **Firewall**, disable **UDP**. 3. Enable **TLS decryption**. -If you wish to apply HTTP filtering to all HTTPS traffic, you must also [disable QUIC](/cloudflare-one/policies/gateway/http-policies/http3/#prevent-inspection-bypass) in your users' browsers, either manually or through your mobile device management (MDM) software. For more information, refer to [HTTP/3 inspection](/cloudflare-one/policies/gateway/http-policies/http3/). +If you wish to apply HTTP filtering to all HTTPS traffic, you must also [disable QUIC](/cloudflare-one/policies/gateway/http-policies/http3/#prevent-inspection-bypass) in your users' browsers, either manually or through your mobile device management (MDM) software. For more information, refer to [HTTP/3 inspection](/cloudflare-one/policies/gateway/http-policies/http3/). ::: diff --git a/src/content/partials/cloudflare-one/gateway/doh-instructions.mdx b/src/content/partials/cloudflare-one/gateway/doh-instructions.mdx index c91cee86b898cc8..f5da3418efafe25 100644 --- a/src/content/partials/cloudflare-one/gateway/doh-instructions.mdx +++ b/src/content/partials/cloudflare-one/gateway/doh-instructions.mdx @@ -18,7 +18,7 @@ Firefox is now configured to use your DoH endpoint. For more information on conf :::note -If you want to enforce DNS policies through WARP instead of over DoH, you can disable DoH for your organization by blocking the [Firefox DoH canary domain](https://support.mozilla.org/kb/canary-domain-use-application-dnsnet). +If you want to enforce DNS policies through WARP instead of over DoH, you can disable DoH for your organization by blocking the [Firefox DoH canary domain](https://support.mozilla.org/kb/canary-domain-use-application-dnsnet). ::: @@ -62,5 +62,5 @@ Read more about [enabling DNS over HTTPS](https://www.chromium.org/developers/dn
-Currently, Safari does not support DNS over HTTPS. +Currently, Safari does not support DNS over HTTPS.
diff --git a/src/content/partials/cloudflare-one/warp/switch-orgs.mdx b/src/content/partials/cloudflare-one/warp/switch-orgs.mdx index 4e31d853379f35b..ee32128e5be3c77 100644 --- a/src/content/partials/cloudflare-one/warp/switch-orgs.mdx +++ b/src/content/partials/cloudflare-one/warp/switch-orgs.mdx @@ -19,5 +19,5 @@ To switch to a different organization as a user: :::note -Only admins can [add additional organizations](#mdm-file-format) to the WARP GUI. To connect to an organization that is not displayed in the GUI, go to {props.two} to manually log out of the old organization and log into the new organization. +Only admins can [add additional organizations](#mdm-file-format) to the WARP GUI. To connect to an organization that is not displayed in the GUI, go to {props.two} to manually log out of the old organization and log into the new organization. ::: diff --git a/src/content/partials/dns/ns-set-omission-callout.mdx b/src/content/partials/dns/ns-set-omission-callout.mdx index 59b5d17695de104..4255ed43dcb62dd 100644 --- a/src/content/partials/dns/ns-set-omission-callout.mdx +++ b/src/content/partials/dns/ns-set-omission-callout.mdx @@ -5,5 +5,5 @@ :::note -If the parameter `ns_set` is omitted, the default set `1` will be assigned. +If the parameter `ns_set` is omitted, the default set `1` will be assigned. ::: diff --git a/src/content/partials/dns/recover-deleted-domain.mdx b/src/content/partials/dns/recover-deleted-domain.mdx index 588e6ede7e44f0a..3408a63acca7bcc 100644 --- a/src/content/partials/dns/recover-deleted-domain.mdx +++ b/src/content/partials/dns/recover-deleted-domain.mdx @@ -7,5 +7,5 @@ To recover a deleted domain, [re-add it in Cloudflare](/fundamentals/setup/manag :::caution -Cloudflare support is unable to restore DNS or settings for deleted domains. +Cloudflare support is unable to restore DNS or settings for deleted domains. ::: diff --git a/src/content/partials/dns/tsig-name-match.mdx b/src/content/partials/dns/tsig-name-match.mdx index 30f6cc00a0f141d..ffaa6bc70ebfc62 100644 --- a/src/content/partials/dns/tsig-name-match.mdx +++ b/src/content/partials/dns/tsig-name-match.mdx @@ -5,5 +5,5 @@ :::note -The TSIG names configured at your primary and secondary DNS providers have to be exactly the same. Any differences in TSIG names will cause zone transfers to fail. +The TSIG names configured at your primary and secondary DNS providers have to be exactly the same. Any differences in TSIG names will cause zone transfers to fail. ::: diff --git a/src/content/partials/email-security/deployment/o365-gcc.mdx b/src/content/partials/email-security/deployment/o365-gcc.mdx index 78dc3e8a0660525..94afd5f4a9ae9d6 100644 --- a/src/content/partials/email-security/deployment/o365-gcc.mdx +++ b/src/content/partials/email-security/deployment/o365-gcc.mdx @@ -5,5 +5,5 @@ :::note -Email Security (formerly Area 1) supports Microsoft Office 365 Government Community Cloud (GCC). Refer to [Microsoft 365 Government Community Cloud](/email-security/reference/office365-gcc/) for more information. +Email Security (formerly Area 1) supports Microsoft Office 365 Government Community Cloud (GCC). Refer to [Microsoft 365 Government Community Cloud](/email-security/reference/office365-gcc/) for more information. ::: diff --git a/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx b/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx index bc5f11c96049985..0f3c8996e8dba65 100644 --- a/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx +++ b/src/content/partials/email-security/deployment/o365-use-case-transport-rules.mdx @@ -45,7 +45,7 @@ To create the transport rules that will send emails with certain *IP address is in any of these ranges or exactly matches* > enter the egress IPs in the [Egress IPs page](/email-security/deployment/inline/reference/egress-ips/). * **Do the following**: *{props.seven}*. - + {/* todo set rule conditions */} 11. Select **Next**. diff --git a/src/content/partials/email-security/deployment/o365-use-cases-antispam.mdx b/src/content/partials/email-security/deployment/o365-use-cases-antispam.mdx index 942c2d3b4c9d0ab..898655b25e54a16 100644 --- a/src/content/partials/email-security/deployment/o365-use-cases-antispam.mdx +++ b/src/content/partials/email-security/deployment/o365-use-cases-antispam.mdx @@ -37,11 +37,11 @@ To configure anti-spam policies: - **Select quarantine policy**: {props.three}. - **Retain spam in quarantine for this many days**: Default is 15 days. Email Security (formerly Area 1) recommends 15-30 days. - Select the spam actions in the above step: - +
- + ![Select the spam actions in the above step](~/assets/images/email-security/deployment/inline-setup/o365-area1-mx/case2-step7-spam.png) - +
8. Select **Save**. diff --git a/src/content/partials/email-security/outbound-email.mdx b/src/content/partials/email-security/outbound-email.mdx index 3d561637a6b103a..1ed881d40a0dd1b 100644 --- a/src/content/partials/email-security/outbound-email.mdx +++ b/src/content/partials/email-security/outbound-email.mdx @@ -5,5 +5,5 @@ :::note[Note] -Email Security (formerly Area 1) does not currently manage outbound email. If you intend to remove other existing services that manage outbound email, you will have to plan accordingly on migrating outbound functions back to your email services (such as Office 365 / Google Workspace). +Email Security (formerly Area 1) does not currently manage outbound email. If you intend to remove other existing services that manage outbound email, you will have to plan accordingly on migrating outbound functions back to your email services (such as Office 365 / Google Workspace). ::: diff --git a/src/content/partials/fundamentals/cybersafe-configuration.mdx b/src/content/partials/fundamentals/cybersafe-configuration.mdx index c0445c39f435f08..387213a3a3cd011 100644 --- a/src/content/partials/fundamentals/cybersafe-configuration.mdx +++ b/src/content/partials/fundamentals/cybersafe-configuration.mdx @@ -9,5 +9,5 @@ To facilitate compliance with CIPA requirements, administrators can [enable a si It is important to note that while our recommended CIPA compliance rule covers the essential filter categories, CIPA is designed to be flexible, allowing administrators to adjust filtering policies based on local standards and requirements. -Administrators should carefully assess their specific location and userbase to determine if additional categories may need to be added or modified to ensure comprehensive protection. +Administrators should carefully assess their specific location and userbase to determine if additional categories may need to be added or modified to ensure comprehensive protection. ::: diff --git a/src/content/partials/fundamentals/ubb-recommendation.mdx b/src/content/partials/fundamentals/ubb-recommendation.mdx index 8efb9fd540de6c7..7e7fc7cd3a8b71a 100644 --- a/src/content/partials/fundamentals/ubb-recommendation.mdx +++ b/src/content/partials/fundamentals/ubb-recommendation.mdx @@ -23,7 +23,7 @@ To set up those notifications: * **Notification email** :::note - Some plans also have access to alerts through [PagerDuty](/notifications/get-started/configure-pagerduty/) and [Webhooks](/notifications/get-started/configure-webhooks/). + Some plans also have access to alerts through [PagerDuty](/notifications/get-started/configure-pagerduty/) and [Webhooks](/notifications/get-started/configure-webhooks/). ::: 6. Select **Save**. diff --git a/src/content/partials/images/anim.mdx b/src/content/partials/images/anim.mdx index dd6e87c2d76edb4..99700d323001b5c 100644 --- a/src/content/partials/images/anim.mdx +++ b/src/content/partials/images/anim.mdx @@ -3,16 +3,16 @@ --- import { Tabs, TabItem } from "~/components" -Whether to preserve animation frames from input files. Default is `true`. Setting it to `false` reduces animations to still images. This setting is recommended when enlarging images or processing arbitrary user content, because large GIF animations can weigh tens or even hundreds of megabytes. It is also useful to set `anim:false` when using `format:"json"` to get the response quicker without the number of frames. +Whether to preserve animation frames from input files. Default is `true`. Setting it to `false` reduces animations to still images. This setting is recommended when enlarging images or processing arbitrary user content, because large GIF animations can weigh tens or even hundreds of megabytes. It is also useful to set `anim:false` when using `format:"json"` to get the response quicker without the number of frames. - ```js + ```js anim=false ``` - ```js + ```js cf: {image: {anim: false}} ``` diff --git a/src/content/partials/images/background.mdx b/src/content/partials/images/background.mdx index e428f31e47b49b1..138e20cf4ef3996 100644 --- a/src/content/partials/images/background.mdx +++ b/src/content/partials/images/background.mdx @@ -3,11 +3,11 @@ --- import { Tabs, TabItem } from "~/components" -Background color to add underneath the image. Applies to images with transparency (for example, PNG) and images resized with `fit=pad`. Accepts any CSS color using CSS4 modern syntax, such as `rgb(255 255 0)` and `rgba(255 255 0 100)`. +Background color to add underneath the image. Applies to images with transparency (for example, PNG) and images resized with `fit=pad`. Accepts any CSS color using CSS4 modern syntax, such as `rgb(255 255 0)` and `rgba(255 255 0 100)`. - ```js + ```js background=%23RRGGBB OR @@ -16,7 +16,7 @@ Background color to add underneath the image. Applies to images with transparenc ``` - ```js + ```js cf: {image: {background: "#RRGGBB"}} ``` diff --git a/src/content/partials/images/blur.mdx b/src/content/partials/images/blur.mdx index c8567d7cc9e3ff0..7fd9756c5290f02 100644 --- a/src/content/partials/images/blur.mdx +++ b/src/content/partials/images/blur.mdx @@ -7,12 +7,12 @@ Blur radius between `1` (slight blur) and `250` (maximum). Be aware that you can - ```js + ```js blur=50 ``` - ```js + ```js cf: {image: {blur: 50}} ``` diff --git a/src/content/partials/images/border.mdx b/src/content/partials/images/border.mdx index 55603fa151ab0fb..ddcd3dddb66247c 100644 --- a/src/content/partials/images/border.mdx +++ b/src/content/partials/images/border.mdx @@ -7,7 +7,7 @@ Adds a border around the image. The border is added after resizing. Border width - ```js + ```js cf: {image: {border: {color: "rgb(0,0,0,0)", top: 5, right: 10, bottom: 5, left: 10}}} cf: {image: {border: {color: "#FFFFFF", width: 10}}} ``` diff --git a/src/content/partials/images/brightness.mdx b/src/content/partials/images/brightness.mdx index 48ca678ba43dca9..4674dd8e893943d 100644 --- a/src/content/partials/images/brightness.mdx +++ b/src/content/partials/images/brightness.mdx @@ -7,12 +7,12 @@ Increase brightness by a factor. A value of `1.0` equals no change, a value of ` - ```js + ```js brightness=0.5 ``` - ```js + ```js cf: {image: {brightness: 0.5}} ``` diff --git a/src/content/partials/images/compression.mdx b/src/content/partials/images/compression.mdx index 80444478fe35fa4..327485198c335b6 100644 --- a/src/content/partials/images/compression.mdx +++ b/src/content/partials/images/compression.mdx @@ -7,12 +7,12 @@ Slightly reduces latency on a cache miss by selecting a quickest-to-compress fil - ```js + ```js compression=fast ``` - ```js + ```js cf: {image: {compression: "fast"}} ``` diff --git a/src/content/partials/images/contrast.mdx b/src/content/partials/images/contrast.mdx index d8105b48df0265e..4e5b3e1ef644434 100644 --- a/src/content/partials/images/contrast.mdx +++ b/src/content/partials/images/contrast.mdx @@ -7,12 +7,12 @@ Increase contrast by a factor. A value of `1.0` equals no change, a value of `0. - ```js + ```js contrast=0.5 ``` - ```js + ```js cf: {image: {contrast: 0.5}} ``` diff --git a/src/content/partials/images/dpr.mdx b/src/content/partials/images/dpr.mdx index 97ebb8f139c52b5..580718675725ae4 100644 --- a/src/content/partials/images/dpr.mdx +++ b/src/content/partials/images/dpr.mdx @@ -7,12 +7,12 @@ Device Pixel Ratio. Default is `1`. Multiplier for `width`/`height` that makes i - ```js + ```js dpr=1 ``` - ```js + ```js cf: {image: {dpr: 1}} ``` diff --git a/src/content/partials/images/fit.mdx b/src/content/partials/images/fit.mdx index 5b8195a2beec913..96f30fdfd578c8e 100644 --- a/src/content/partials/images/fit.mdx +++ b/src/content/partials/images/fit.mdx @@ -10,12 +10,12 @@ Affects interpretation of `width` and `height`. All resizing modes preserve aspe - ```js + ```js fit=scale-down ``` - ```js + ```js cf: {image: {fit: "scale-down"}} ``` @@ -26,12 +26,12 @@ Affects interpretation of `width` and `height`. All resizing modes preserve aspe - ```js + ```js fit=contain ``` - ```js + ```js cf: {image: {fit: "contain"}} ``` @@ -42,12 +42,12 @@ Affects interpretation of `width` and `height`. All resizing modes preserve aspe - ```js + ```js fit=cover ``` - ```js + ```js cf: {image: {fit: "cover"}} ``` @@ -58,12 +58,12 @@ Affects interpretation of `width` and `height`. All resizing modes preserve aspe - ```js + ```js fit=crop ``` - ```js + ```js cf: {image: {fit: "crop"}} ``` @@ -74,12 +74,12 @@ Affects interpretation of `width` and `height`. All resizing modes preserve aspe - ```js + ```js fit=pad ``` - ```js + ```js cf: {image: {fit: "pad"}} ``` diff --git a/src/content/partials/images/format.mdx b/src/content/partials/images/format.mdx index e141207c99dbc99..f82ca817e4eba46 100644 --- a/src/content/partials/images/format.mdx +++ b/src/content/partials/images/format.mdx @@ -19,17 +19,17 @@ Workers integration supports: - ```js + ```js format=auto ``` - ```js + ```js f=auto ``` - ```js + ```js cf: {image: {format: "avif"}} ``` diff --git a/src/content/partials/images/gamma.mdx b/src/content/partials/images/gamma.mdx index c7bd8fa40065fc7..adb202c63122930 100644 --- a/src/content/partials/images/gamma.mdx +++ b/src/content/partials/images/gamma.mdx @@ -7,12 +7,12 @@ Increase exposure by a factor. A value of `1.0` equals no change, a value of `0. - ```js + ```js gamma=0.5 ``` - ```js + ```js cf: {image: {gamma: 0.5}} ``` diff --git a/src/content/partials/images/gravity.mdx b/src/content/partials/images/gravity.mdx index 1b1442f0e344712..c6b3aac9352e0eb 100644 --- a/src/content/partials/images/gravity.mdx +++ b/src/content/partials/images/gravity.mdx @@ -10,17 +10,17 @@ When cropping with `fit: "cover"` and `fit: "crop"`, this parameter defines the - ```js + ```js gravity=auto ``` - ```js + ```js g=auto ``` - ```js + ```js cf: {image: {gravity: "auto"}} ``` @@ -37,7 +37,7 @@ You must subtract the height of the image before you calculate the focal point. - ```js + ```js gravity=left or @@ -46,12 +46,12 @@ You must subtract the height of the image before you calculate the focal point. ``` - ```js + ```js cf: {image: {gravity: "right"}} or - cf: {image: {gravity: {x:0.5, y:0.2}}} + cf: {image: {gravity: {x:0.5, y:0.2}}} ``` \ No newline at end of file diff --git a/src/content/partials/images/height.mdx b/src/content/partials/images/height.mdx index 78ceed0844359bd..fa6d30670f63a0a 100644 --- a/src/content/partials/images/height.mdx +++ b/src/content/partials/images/height.mdx @@ -7,17 +7,17 @@ Specifies maximum height of the image in pixels. Exact behavior depends on the ` - ```js + ```js height=250 ``` - ```js + ```js h=250 ``` - ```js + ```js cf: {image: {height: 250}} ``` diff --git a/src/content/partials/images/metadata.mdx b/src/content/partials/images/metadata.mdx index 1fc0cbecdf974a2..cfbf2d30e48f810 100644 --- a/src/content/partials/images/metadata.mdx +++ b/src/content/partials/images/metadata.mdx @@ -3,7 +3,7 @@ --- import { Tabs, TabItem } from "~/components" -Controls amount of invisible metadata (EXIF data) that should be preserved. +Controls amount of invisible metadata (EXIF data) that should be preserved. Color profiles and EXIF rotation are applied to the image even if the metadata is discarded. Content Credentials (C2PA metadata) may be preserved if the [setting is enabled](/images/transform-images/preserve-content-credentials). @@ -23,12 +23,12 @@ Options include: - ```js + ```js metadata=copyright ``` - ```js + ```js cf: {image: {metadata: "copyright"}} ``` @@ -36,16 +36,16 @@ Options include: * `keep`\ Preserves most of EXIF metadata, including GPS location if present. - If C2PA metadata preservation is enabled, then this option will preserve all Content Credentials. + If C2PA metadata preservation is enabled, then this option will preserve all Content Credentials. - ```js + ```js metadata=keep ``` - ```js + ```js cf: {image: {metadata: "keep"}} ``` @@ -56,12 +56,12 @@ Options include: - ```js + ```js metadata=none ``` - ```js + ```js cf: {image: {metadata: "none"}} ``` diff --git a/src/content/partials/images/onerror.mdx b/src/content/partials/images/onerror.mdx index 772e4874848834f..d253060a404d34e 100644 --- a/src/content/partials/images/onerror.mdx +++ b/src/content/partials/images/onerror.mdx @@ -11,7 +11,7 @@ In case of a fatal error that prevents the image from being resized, redirects t - ```js + ```js onerror=redirect ``` diff --git a/src/content/partials/images/quality.mdx b/src/content/partials/images/quality.mdx index e72011a0e60f800..1e3d7ed0c414e41 100644 --- a/src/content/partials/images/quality.mdx +++ b/src/content/partials/images/quality.mdx @@ -11,17 +11,17 @@ Specifies quality for images in JPEG, WebP, and AVIF formats. The quality is in - ```js + ```js quality=50 ``` - ```js + ```js q=50 ``` - ```js + ```js cf: {image: {quality: 50}} ``` diff --git a/src/content/partials/images/rotate.mdx b/src/content/partials/images/rotate.mdx index d8ee64657c8fa2c..d16312d76f29b76 100644 --- a/src/content/partials/images/rotate.mdx +++ b/src/content/partials/images/rotate.mdx @@ -7,12 +7,12 @@ Number of degrees (`90`, `180`, or `270`) to rotate the image by. `width` and `h - ```js + ```js rotate=90 ``` - ```js + ```js cf: {image: {rotate: 90}} ``` diff --git a/src/content/partials/images/saturation.mdx b/src/content/partials/images/saturation.mdx index 1df693f6a3c30a6..10a01ab8269c793 100644 --- a/src/content/partials/images/saturation.mdx +++ b/src/content/partials/images/saturation.mdx @@ -7,12 +7,12 @@ Increases saturation by a factor. A value of `1.0` equals no change, a value of - ```js + ```js saturation=0.5 ``` - ```js + ```js cf: {image: {saturation: 0.5}} ``` diff --git a/src/content/partials/images/sharpen.mdx b/src/content/partials/images/sharpen.mdx index 8133cd9905c219d..0e24ca315660d8d 100644 --- a/src/content/partials/images/sharpen.mdx +++ b/src/content/partials/images/sharpen.mdx @@ -3,16 +3,16 @@ --- import { Tabs, TabItem } from "~/components" -Specifies strength of sharpening filter to apply to the image. The value is a floating-point number between `0` (no sharpening, default) and `10` (maximum). `1` is a recommended value for downscaled images. +Specifies strength of sharpening filter to apply to the image. The value is a floating-point number between `0` (no sharpening, default) and `10` (maximum). `1` is a recommended value for downscaled images. - ```js + ```js sharpen=2 ``` - ```js + ```js cf: {image: {sharpen: 2}} ``` diff --git a/src/content/partials/images/trim.mdx b/src/content/partials/images/trim.mdx index 24b541131ef20de..a2c4f558f40cfdf 100644 --- a/src/content/partials/images/trim.mdx +++ b/src/content/partials/images/trim.mdx @@ -7,7 +7,7 @@ Specifies a number of pixels to cut off on each side. Allows removal of borders - ```js + ```js trim=20;30;20;0 trim.width=678 trim.height=678 @@ -16,7 +16,7 @@ Specifies a number of pixels to cut off on each side. Allows removal of borders ``` - ```js + ```js cf: {image: {trim: {top: 12, right: 78, bottom: 34, left: 56, width:678, height:678}}} ``` diff --git a/src/content/partials/images/width.mdx b/src/content/partials/images/width.mdx index 6ac95f4de60b8d7..0ed9f0c4d69eeb2 100644 --- a/src/content/partials/images/width.mdx +++ b/src/content/partials/images/width.mdx @@ -9,17 +9,17 @@ Available options are a specified width in pixels or `auto`. - ```js + ```js width=250 ``` - ```js + ```js w=250 ``` - ```js + ```js cf: {image: {width: 250}} ``` diff --git a/src/content/partials/kv/kv-vs-d1.mdx b/src/content/partials/kv/kv-vs-d1.mdx index 879e028c5396a4f..c673ac237637575 100644 --- a/src/content/partials/kv/kv-vs-d1.mdx +++ b/src/content/partials/kv/kv-vs-d1.mdx @@ -8,7 +8,7 @@ Cloudflare Workers KV provides an eventually consistent global key-value store t low read latency for hot reads to keys. This is ideal for storing data that is repeatedly read by your Workers, such as configuration data, user preferences, cached values, etc. Workers KV can sustain high read throughput (unlimited requests per second per key) with \<5ms latency globally for hot reads. Workers KV is eventually consistent, so writes may take up to 60 seconds to propagate through Cloudflare's network by default. Cloudflare D1 provides a SQL database that supports relational data modeling and querying. D1 supports snapshot isolation consistency and is ideal for -workloads that store user data or general web application data. +workloads that store user data or general web application data. - Use Workers KV if you need to store and access configuration data that will be read by Workers frequently, is written infrequently (\<1 RPS per key) and can tolerate eventual consistency. - Use D1 if you need to store general application data, need SQL access to your data, and require strong consistency (writes are immediately visible after being committed). diff --git a/src/content/partials/learning-paths/zero-trust/configure-idp.mdx b/src/content/partials/learning-paths/zero-trust/configure-idp.mdx index 00cdee8fd84076e..9aaf4630115caa3 100644 --- a/src/content/partials/learning-paths/zero-trust/configure-idp.mdx +++ b/src/content/partials/learning-paths/zero-trust/configure-idp.mdx @@ -9,7 +9,7 @@ An diff --git a/src/content/partials/learning-paths/zero-trust/private-dns.mdx b/src/content/partials/learning-paths/zero-trust/private-dns.mdx index 0ac2c40e1f7f1be..9e00d2e2df4a3cc 100644 --- a/src/content/partials/learning-paths/zero-trust/private-dns.mdx +++ b/src/content/partials/learning-paths/zero-trust/private-dns.mdx @@ -36,7 +36,7 @@ To add a domain to the Local Domain Fallback list: :::note -Only available on Enterprise plans. +Only available on Enterprise plans. ::: [Custom resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) provide similar functionality to Local Domain Fallback but occur in Cloudflare Gateway rather than on the local device. This option is recommended if you want more granular control over private DNS resolution. For example, you can ensure that all users in a specific geography use the private DNS server closest to them, ensure that specific conditions are met before resolving private DNS traffic, and apply [Gateway DNS policies](/cloudflare-one/policies/gateway/dns-policies/) to private DNS traffic. diff --git a/src/content/partials/logs/filtering-limitations.mdx b/src/content/partials/logs/filtering-limitations.mdx index 94f8c8d8ab04660..6ab2216d4bca47d 100644 --- a/src/content/partials/logs/filtering-limitations.mdx +++ b/src/content/partials/logs/filtering-limitations.mdx @@ -7,5 +7,5 @@ Filtering is not supported on the following data types: `objects`, `array[object]`. -For the Firewall events dataset, the following fields are not supported: `Action`, `Kind`, `MatchIndex`, `Metadata`, `OriginatorRayID`, `RuleID`, and `Source`. +For the Firewall events dataset, the following fields are not supported: `Action`, `Kind`, `MatchIndex`, `Metadata`, `OriginatorRayID`, `RuleID`, and `Source`. ::: diff --git a/src/content/partials/rules/page-rules-migration.mdx b/src/content/partials/rules/page-rules-migration.mdx index d0c69b6e6541ebb..0f2cbdae964a417 100644 --- a/src/content/partials/rules/page-rules-migration.mdx +++ b/src/content/partials/rules/page-rules-migration.mdx @@ -7,5 +7,5 @@ Consider alternative [Rules](/rules/) options due to their enhanced configurability. Refer to the [migration guide](/rules/reference/page-rules-migration/) for details. -For more flexibility and customization, consider using [Snippets](/rules/snippets/). +For more flexibility and customization, consider using [Snippets](/rules/snippets/). ::: diff --git a/src/content/partials/ruleset-engine/rule-position-values.mdx b/src/content/partials/ruleset-engine/rule-position-values.mdx index 71388c839fca01e..aed905dee8894cd 100644 --- a/src/content/partials/ruleset-engine/rule-position-values.mdx +++ b/src/content/partials/ruleset-engine/rule-position-values.mdx @@ -11,5 +11,5 @@ :::caution[Important] -You can only use one of the `before`, `after`, and `index` fields at a time. +You can only use one of the `before`, `after`, and `index` fields at a time. ::: diff --git a/src/content/partials/security-center/scan-properties.mdx b/src/content/partials/security-center/scan-properties.mdx index f7a1fd0f3b365f5..aa07143a1e7c4f7 100644 --- a/src/content/partials/security-center/scan-properties.mdx +++ b/src/content/partials/security-center/scan-properties.mdx @@ -3,7 +3,7 @@ --- -* **Severity**: The security risk of the insight. The severity values are: *Moderate*, *High*, and *Critical*. The higher the severity level, the higher the risk of threat to your environment. +* **Severity**: The security risk of the insight. The severity values are: *Moderate*, *High*, and *Critical*. The higher the severity level, the higher the risk of threat to your environment. * **Insight**: The insight description detailing the current configuration that is causing the risk or vulnerability. * **Risk**: A description of the risk associated with not addressing the issue. * **Type**: The insight category. diff --git a/src/content/partials/security-center/temporary-disable.mdx b/src/content/partials/security-center/temporary-disable.mdx index 2b782dd2e0e7a72..671cf9365621eac 100644 --- a/src/content/partials/security-center/temporary-disable.mdx +++ b/src/content/partials/security-center/temporary-disable.mdx @@ -7,5 +7,5 @@ import { Markdown } from "~/components" :::caution[Temporarily Disabled] -The {props.one} tab is temporarily disabled and not visible in the Cloudflare Dashboard at the moment. +The {props.one} tab is temporarily disabled and not visible in the Cloudflare Dashboard at the moment. ::: diff --git a/src/content/partials/ssl/ciphers-tls-1.3-array-callout.mdx b/src/content/partials/ssl/ciphers-tls-1.3-array-callout.mdx index 7284d395e1ab1c0..926b062540e2166 100644 --- a/src/content/partials/ssl/ciphers-tls-1.3-array-callout.mdx +++ b/src/content/partials/ssl/ciphers-tls-1.3-array-callout.mdx @@ -5,5 +5,5 @@ :::note -The following array does not include the TLS 1.3 ciphers. To use them, you should [enable TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/#enable-tls-13) on your zone. For details, refer to [Cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/#tls-13). +The following array does not include the TLS 1.3 ciphers. To use them, you should [enable TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/#enable-tls-13) on your zone. For details, refer to [Cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/#tls-13). ::: diff --git a/src/content/partials/ssl/cloudflare-managed-client-cert.mdx b/src/content/partials/ssl/cloudflare-managed-client-cert.mdx index fb265fab521d6a0..0f978a5667c9be3 100644 --- a/src/content/partials/ssl/cloudflare-managed-client-cert.mdx +++ b/src/content/partials/ssl/cloudflare-managed-client-cert.mdx @@ -7,5 +7,5 @@ By default, API Shield mTLS uses client certificates issued by a Cloudflare Managed CA. Cloudflare generates a unique CA for each account. -If you need to use certificates issued by another CA, you can use the API to [bring your own CA for mTLS](/ssl/client-certificates/byo-ca/). +If you need to use certificates issued by another CA, you can use the API to [bring your own CA for mTLS](/ssl/client-certificates/byo-ca/). ::: diff --git a/src/content/partials/style-guide/hello.mdx b/src/content/partials/style-guide/hello.mdx index 2fefdcfb8641b71..80d3b8d7472f4b5 100644 --- a/src/content/partials/style-guide/hello.mdx +++ b/src/content/partials/style-guide/hello.mdx @@ -2,7 +2,7 @@ params: - name --- - + Hello, {props.name}! Hello `{props.name}` diff --git a/src/content/partials/support/2fa-enable.mdx b/src/content/partials/support/2fa-enable.mdx index 46711d2ce9be44a..c20907c1901b414 100644 --- a/src/content/partials/support/2fa-enable.mdx +++ b/src/content/partials/support/2fa-enable.mdx @@ -9,7 +9,7 @@ We recommend that all Cloudflare user account holders enable two-factor authenti :::caution -Super Administrators can turn on **2FA Enforcement** to require all members to enable 2FA. If you are not a Super Administrator, you will be forced to turn on 2FA prior to accepting the invitation to join a Cloudflare account as a member. +Super Administrators can turn on **2FA Enforcement** to require all members to enable 2FA. If you are not a Super Administrator, you will be forced to turn on 2FA prior to accepting the invitation to join a Cloudflare account as a member. ::: To enable two-factor authentication for your Cloudflare login: diff --git a/src/content/partials/support/2fa-overview.mdx b/src/content/partials/support/2fa-overview.mdx index fe49e241f387b0e..fb349dcd62261cc 100644 --- a/src/content/partials/support/2fa-overview.mdx +++ b/src/content/partials/support/2fa-overview.mdx @@ -7,7 +7,7 @@ Two-factor authentication (2FA) allows user account owners to add an additional :::note -Cloudflare user accounts configured to use single sign-on (SSO) cannot configure 2FA. +Cloudflare user accounts configured to use single sign-on (SSO) cannot configure 2FA. ::: Cloudflare offers the option to use either a phishing-resistant security key, like a YubiKey, or a Time-Based One-Time password (TOTP) mobile app for authentication, like Google Authenticator, or both. If you add both of these authentication methods to your account, you are initially prompted to log in with the security key, but can opt-out and use TOTP instead. @@ -16,7 +16,7 @@ To ensure that you can securely access your account even without your mobile dev :::note[Tip] -After downloading your backup codes, we recommend saving them in a secure location. +After downloading your backup codes, we recommend saving them in a secure location. ::: As the user account owner, you are automatically assigned the [Super Administrator](/fundamentals/setup/manage-members/) role. Once 2FA is enabled, all Cloudflare account members are required to configure 2FA on their mobile devices. diff --git a/src/content/partials/turnstile/siteverify-warning.mdx b/src/content/partials/turnstile/siteverify-warning.mdx index 32f3a4924f16039..1f0be698c2a4ef5 100644 --- a/src/content/partials/turnstile/siteverify-warning.mdx +++ b/src/content/partials/turnstile/siteverify-warning.mdx @@ -5,5 +5,5 @@ :::caution[Warning] -It is critical to enforce Turnstile tokens with the siteverify API. The Turnstile token could be invalid, expired, or already redeemed. Not verifying the token will leave major vulnerabilities in your implementation. +It is critical to enforce Turnstile tokens with the siteverify API. The Turnstile token could be invalid, expired, or already redeemed. Not verifying the token will leave major vulnerabilities in your implementation. ::: diff --git a/src/content/partials/turnstile/turnstile/siteverify-warning.mdx b/src/content/partials/turnstile/turnstile/siteverify-warning.mdx index 32f3a4924f16039..1f0be698c2a4ef5 100644 --- a/src/content/partials/turnstile/turnstile/siteverify-warning.mdx +++ b/src/content/partials/turnstile/turnstile/siteverify-warning.mdx @@ -5,5 +5,5 @@ :::caution[Warning] -It is critical to enforce Turnstile tokens with the siteverify API. The Turnstile token could be invalid, expired, or already redeemed. Not verifying the token will leave major vulnerabilities in your implementation. +It is critical to enforce Turnstile tokens with the siteverify API. The Turnstile token could be invalid, expired, or already redeemed. Not verifying the token will leave major vulnerabilities in your implementation. ::: diff --git a/src/content/partials/version-management/edit-version.mdx b/src/content/partials/version-management/edit-version.mdx index a65fa3a724d3b51..384b842632fa7b6 100644 --- a/src/content/partials/version-management/edit-version.mdx +++ b/src/content/partials/version-management/edit-version.mdx @@ -16,7 +16,7 @@ To change between different versions of your zone: :::note -If you are on a product that is not available for versioning, you will not be able to switch to another version, and can only make changes under your Global Configuration. +If you are on a product that is not available for versioning, you will not be able to switch to another version, and can only make changes under your Global Configuration. ::: The Domain Summary is accessible from all pages and allows you to quickly switch between versions and domains. diff --git a/src/content/partials/waiting-room/queue-all.mdx b/src/content/partials/waiting-room/queue-all.mdx index 0fcc6dbfb5a1adf..f8625465ac3beeb 100644 --- a/src/content/partials/waiting-room/queue-all.mdx +++ b/src/content/partials/waiting-room/queue-all.mdx @@ -15,7 +15,7 @@ To start queueing all new visitors without a scheduled event: :::note[Note] -Only new visitors will be queued. Active users that are already on your website will continue there and will not return to the queue until their session expires. +Only new visitors will be queued. Active users that are already on your website will continue there and will not return to the queue until their session expires. ::: 4. To begin allowing visitors to the path protected by your waiting room, set **Queue-all** to **Off**. diff --git a/src/content/partials/waiting-room/waiting-room/queue-all.mdx b/src/content/partials/waiting-room/waiting-room/queue-all.mdx index 0fcc6dbfb5a1adf..f8625465ac3beeb 100644 --- a/src/content/partials/waiting-room/waiting-room/queue-all.mdx +++ b/src/content/partials/waiting-room/waiting-room/queue-all.mdx @@ -15,7 +15,7 @@ To start queueing all new visitors without a scheduled event: :::note[Note] -Only new visitors will be queued. Active users that are already on your website will continue there and will not return to the queue until their session expires. +Only new visitors will be queued. Active users that are already on your website will continue there and will not return to the queue until their session expires. ::: 4. To begin allowing visitors to the path protected by your waiting room, set **Queue-all** to **Off**. diff --git a/src/content/partials/workers/workers_sites.mdx b/src/content/partials/workers/workers_sites.mdx index b7f0bb880b0fcb2..0c32b6f127ba498 100644 --- a/src/content/partials/workers/workers_sites.mdx +++ b/src/content/partials/workers/workers_sites.mdx @@ -5,5 +5,5 @@ :::caution[Use Workers Static Assets Instead] -You should use [Workers Static Assets](/workers/static-assets/) to host full-stack applications instead of Workers Sites. Do not use Workers Sites for new projects. +You should use [Workers Static Assets](/workers/static-assets/) to host full-stack applications instead of Workers Sites. Do not use Workers Sites for new projects. :::