Hyperlint Automation: Meta Description Fixes (#20471)

* Fix issue: WorkspaceTaskSubType.META_DESCRIPTION

* Fix issue: WorkspaceTaskSubType.META_DESCRIPTION

* Update src/content/docs/cloudflare-one/identity/authorization-cookie/application-token.mdx

* Update src/content/docs/cloudflare-one/identity/authorization-cookie/index.mdx

* Update src/content/docs/cloudflare-one/identity/authorization-cookie/application-token.mdx

---------

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
Co-authored-by: ranbel <[email protected]>

Author: 2 people

src/content/docs/cloudflare-one/identity/authorization-cookie/application-token.mdx

@@ -3,6 +3,7 @@ pcx_content_type: reference
 title: Application token
 sidebar:
   order: 2
+description: Learn how Cloudflare Access uses application tokens to secure your origin. Understand JWT structure and payloads.
 ---
 
 Cloudflare Access includes the application token with all authenticated requests to your origin. A typical JWT looks like this:

src/content/docs/cloudflare-one/identity/authorization-cookie/index.mdx

@@ -1,6 +1,7 @@
 ---
 pcx_content_type: concept
 title: Authorization cookie
+description: Learn how Cloudflare Access uses CF_Authorization cookies to secure self-hosted web applications.
 sidebar:
   order: 12
 
@@ -9,7 +10,6 @@ sidebar:
 import { Details, GlossaryTooltip } from "~/components"
 
 When you protect a site with Cloudflare Access, Cloudflare checks every HTTP request bound for that site to ensure that the request has a valid `CF_Authorization` cookie. If a request does not include the cookie, Access will block the request.
-
 ## Access JWTs
 
 The `CF_Authorization` cookie contains the user's identity in the form of a JSON Web Token (JWT). Cloudflare securely creates these tokens through the OAUTH or SAML integration between Cloudflare Access and the configured identity provider.