Skip to content

Commit 000db9d

Browse files
feedback
1 parent c969d2a commit 000db9d

File tree

4 files changed

+7
-9
lines changed

4 files changed

+7
-9
lines changed

src/content/docs/api-shield/management-and-monitoring/developer-portal.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ To create a developer portal:
2323
:::note
2424
If you do not have a schema to upload or to select from a pre-existing schema, export your Endpoint Management schema. For best results, include the learned parameters.
2525

26-
Only <GlossaryTooltip term="API schema">API schemas</GlossaryTooltip> uploaded to Schema validation 2.0 are available when selecting existing schemas
26+
Only <GlossaryTooltip term="API schema">API schemas</GlossaryTooltip> uploaded to Schema validation 2.0 are available when selecting existing schemas.
2727
:::
2828
5. Select **Download project files** to save a local copy of the files that will be uploaded to Cloudflare Pages. Downloading the project files can be helpful if you wish to modify the project in any way and then upload the new version manually to Pages.
2929
6. Select **Create pages project** to begin project creation. A new Pages project will be automatically created and your API schema will be automatically uploaded to the project along with other supporting static content.
@@ -40,7 +40,7 @@ To create a developer portal:
4040
:::note
4141
If you do not have a schema to upload or to select from a pre-existing schema, export your Endpoint Management schema. For best results, include the learned parameters.
4242

43-
Only <GlossaryTooltip term="API schema">API schemas</GlossaryTooltip> uploaded to Schema validation 2.0 are available when selecting existing schemas
43+
Only <GlossaryTooltip term="API schema">API schemas</GlossaryTooltip> uploaded to Schema validation 2.0 are available when selecting existing schemas.
4444
:::
4545
5. Select **Download project files** to save a local copy of the files that will be uploaded to Cloudflare Pages. Downloading the project files can be helpful if you wish to modify the project in any way and then upload the new version manually to Pages.
4646
6. Select **Create pages project** to begin project creation. A new Pages project will be automatically created and your API schema will be automatically uploaded to the project along with other supporting static content.

src/content/docs/api-shield/management-and-monitoring/endpoint-labels.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ Cloudflare will only add authentication labels to endpoints with successful resp
112112
4. Under **Endpoint labels**, select **Manage label**.
113113
5. Name the label and add an optional label description.
114114
6. Apply the label to your selected endpoints.
115-
7. Select Create label.
115+
7. Select **Create label**.
116116
</Steps>
117117
Alternatively, you can create a user-defined label via **Security** > **Web Assets**.
118118
<Steps>
@@ -170,7 +170,7 @@ Cloudflare will only add authentication labels to endpoints with successful resp
170170
2. Go to **Security** > **Settings**.
171171
3. Filter by **API abuse**.
172172
4. On **Endpoint labels**, select **Manage labels**.
173-
5. On the existing label that you want to apply to multiple endpoints, select Bulk apply.
173+
5. On the existing label that you want to apply to multiple endpoints, select **Bulk apply**.
174174
6. Choose the endpoints that you want to label by selecting its checkbox.
175175
7. Select **Apply label**.
176176
</Steps>

src/content/docs/api-shield/management-and-monitoring/endpoint-management/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ There are two ways to add API endpoints from Discovery.
9393
<Steps>
9494
1. Add a schema by [configuring Schema validation](/api-shield/security/schema-validation/).
9595
2. On **Review schema endpoints**, save new endpoints to endpoint management by checking the box.
96-
3. Select **Save as draft** or **Save and Deploy**. Endpoints will be saved regardless of whether the Schema is saved as a draft or published.
96+
3. Select **Save as draft** or **Save and Deploy**. Endpoints will be saved regardless of whether the schema is saved as a draft or published.
9797
</Steps>
9898
</TabItem>
9999
<TabItem label="New dashboard" icon="rocket">

src/content/docs/api-shield/security/jwt-validation/index.mdx

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -56,8 +56,7 @@ To automatically keep your JWKS up to date when your identity provider refreshes
5656
<Steps>
5757
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
5858
2. Go to **Security** > **API Shield** > **API Rules**.
59-
3. <a id="rule-form"/>
60-
Add a name for your rule.
59+
3. Add a name for your rule.
6160
4. Select a hostname to protect requests with saved endpoints using the rule.
6261
5. Deselect any endpoints that you want JWT validation to ignore (for example, an endpoint used to generate a JWT).
6362
6. Select the token validation configuration that corresponds to the incoming requests.
@@ -73,8 +72,7 @@ To automatically keep your JWKS up to date when your identity provider refreshes
7372
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
7473
2. Go to **Security** > **Security rules**.
7574
3. On API JWT validation rules, select **Create rule**.
76-
4. <a id="rule-form"/>
77-
Add a name for your rule.
75+
4. Add a name for your rule.
7876
5. Select a hostname to protect requests with saved endpoints using the rule.
7977
6. Deselect any endpoints that you want JWT validation to ignore (for example, an endpoint used to generate a JWT).
8078
7. Select the token validation configuration that corresponds to the incoming requests.

0 commit comments

Comments
 (0)