fix(docs): fix linting issues - trailing spaces and EOF newline by ossdhaval · Pull Request #12766 · JanssenProject/jans (original) (raw)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b7b0d02 and 34dac45.

📒 Files selected for processing (50) 

Learnt from: ossdhaval
Repo: JanssenProject/jans PR: 12539
File: docs/janssen-server/auth-server/client-management/software-statements.md:29-29
Timestamp: 2025-10-30T15:21:12.720Z
Learning: In the Janssen Project documentation (docs/ directory), relative links in markdown files work correctly when tested locally even when intermediate directory segments like "janssen-server" appear to be missing from the relative path. The documentation build system handles path resolution appropriately, so local testing by developers is authoritative for verifying link correctness.

📚 Learning: 2025-11-18T07:43:55.761Z 

Learnt from: pujavs
Repo: JanssenProject/jans PR: 12704
File: jans-config-api/docs/jans-config-api-swagger.yaml:17540-17546
Timestamp: 2025-11-18T07:43:55.761Z
Learning: The file `jans-config-api/docs/jans-config-api-swagger.yaml` is auto-generated with dependent modules changes and metadata. The config API does not override it.

Applied to files:

Learnt from: moabu
Repo: JanssenProject/jans PR: 12687
File: terraform-provider-jans/jans/schemas.go:44-61
Timestamp: 2025-11-14T12:07:49.986Z
Learning: In terraform-provider-jans/jans/schemas.go, the SCIM schema endpoints (/jans-scim/restv1/v2/Schemas/) are public discovery endpoints per RFC 7644 and do not require OAuth scopes or authentication tokens. The GetSchemas and GetSchema methods intentionally pass empty strings for token and scope parameters.

Applied to files:

Learnt from: yuriyz
Repo: JanssenProject/jans PR: 12596
File: docs/janssen-server/auth-server/tokens/oauth-tx-tokens.md:146-257
Timestamp: 2025-11-19T12:55:01.596Z
Learning: In the Janssen project, the TxToken custom script documentation is intentionally duplicated in both `docs/janssen-server/auth-server/tokens/oauth-tx-tokens.md` and `docs/script-catalog/tx_token/txtoken.md` to provide easy access from both the transaction token documentation and the script catalog.

Applied to files:

[high] 662-662: Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.

(curl-auth-header)

🪛 LanguageTool docs/janssen-server/auth-server/endpoints/authorization-challenge.md

[style] ~29-~29: Consider a more concise word here.
Context: ...ns-auth/restv1/authorize-challenge ``` In order to call Authorization Challenge Endpoint c...

(IN_ORDER_TO_PREMIUM)

docs/janssen-server/auth-server/endpoints/client-registration.md

[grammar] ~24-~24: Ensure spelling is correct
Context: ...aim of the OpenID Connect configuration reponse, typically deployed at ```text https:/...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

docs/janssen-server/auth-server/endpoints/authorization.md

[style] ~138-~138: ‘in the meantime’ might be wordy. Consider a shorter alternative.
Context: ...t you'd like to contribute to this page in the meantime, you can get started with our [Contribu...

(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)

docs/janssen-server/auth-server/logging/audit-logs.md

[style] ~56-~56: ‘in the meantime’ might be wordy. Consider a shorter alternative.
Context: ...t you'd like to contribute to this page in the meantime, you can get started with our [Contribu...

(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)

docs/janssen-server/auth-server/endpoints/archived-jwks-uri.md

[style] ~45-~45: ‘in the meantime’ might be wordy. Consider a shorter alternative.
Context: ...t you'd like to contribute to this page in the meantime, you can get started with our [Contribu...

(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)

docs/janssen-server/auth-server/crypto/keys.md

[style] ~11-~11: Consider using a more concise synonym.
Context: ...gorithms in salted and unsalted, to fit a variety of business needs. If other algorithms are...

(A_VARIETY_OF)

docs/janssen-server/auth-server/logging/custom-logs.md

[style] ~24-~24: ‘in the meantime’ might be wordy. Consider a shorter alternative.
Context: ...t you'd like to contribute to this page in the meantime, you can get started with our [Contribu...

(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)

docs/janssen-server/auth-server/endpoints/jwks-uri.md

[style] ~44-~44: ‘in the meantime’ might be wordy. Consider a shorter alternative.
Context: ...t you'd like to contribute to this page in the meantime, you can get started with our [Contribu...

(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)

docs/janssen-server/auth-server/endpoints/end-session.md

[grammar] ~25-~25: Ensure spelling is correct
Context: ...ession endpoint. By default, end session ndpoint looks like below: ``` https://janssen....

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

docs/janssen-server/auth-server/endpoints/par.md

[style] ~182-~182: ‘in the meantime’ might be wordy. Consider a shorter alternative.
Context: ...t you'd like to contribute to this page in the meantime, you can get started with our [Contribu...

(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)

docs/janssen-server/auth-server/endpoints/userinfo.md

[grammar] ~49-~49: Use a hyphen to join words.
Context: ...s. Since userinfo endpoint is an OAuth2 protected resource, a valid access token...

(QB_NEW_EN_HYPHEN)

docs/janssen-server/auth-server/logging/log4j2.md

[style] ~170-~170: ‘in the meantime’ might be wordy. Consider a shorter alternative.
Context: ...t you'd like to contribute to this page in the meantime, you can get started with our [Contribu...

(EN_WORDINESS_PREMIUM_IN_THE_MEANTIME)

docs/janssen-server/auth-server/client-management/client-authn.md

[grammar] ~89-~89: Use a hyphen to join words.
Context: ...ey_jwt private_key_jwt is private key based method where secret is not shared ...

(QB_NEW_EN_HYPHEN)

[grammar] ~96-~96: Ensure spelling is correct
Context: ...ns without client having to update JWKS manualy. Check jwks and jwks_uri elements i...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

docs/janssen-server/auth-server/endpoints/access-evaluation.md

[style] ~61-~61: Consider a more concise word here.
Context: ...s-auth/restv1/access/v1/evaluation ``` In order to call Access Evaluation Endpoint client ...

(IN_ORDER_TO_PREMIUM)

🪛 markdownlint-cli2 (0.18.1) docs/janssen-server/auth-server/endpoints/authorization-challenge.md

26-26: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

150-150: Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)

docs/janssen-server/auth-server/endpoints/client-registration.md

43-43: Link text should be descriptive

(MD059, descriptive-link-text)

docs/janssen-server/auth-server/endpoints/authorization.md

26-26: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

docs/janssen-server/auth-server/authz-details/README.md

46-46: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)

47-47: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)

48-48: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)

69-69: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

84-84: Images should have alternate text (alt text)

(MD045, no-alt-text)

docs/janssen-server/auth-server/endpoints/archived-jwks-uri.md

45-45: Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)

docs/janssen-server/auth-server/endpoints/end-session.md

26-26: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

29-29: Trailing spaces
Expected: 0 or 2; Actual: 1

(MD009, no-trailing-spaces)

docs/janssen-server/auth-server/endpoints/access-evaluation.md

58-58: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

docs/janssen-server/auth-server/endpoints/backchannel-authentication.md (1)

384-384: You better think twice if you skip good linting vibes! This one's solid.

Adding the trailing newline at EOF is exactly the kind of standards-compliant housekeeping that keeps documentation clean and CI happy. The content and structure remain unchanged—this is pure formatting hygiene, and it's the right call.

docs/janssen-server/auth-server/endpoints/global-token-revocation.md (1)

12-13: You better think twice—let me bird-dog this formatting cleanup!

The line reflows look sensible and break at reasonable clause boundaries for readability. Lines 12–13 split a long sentence naturally ("allow greater" | "control and management"), and lines 34–35 adjust the paragraph flow in the Usage section without mangling meaning. Minor text on line 55 is a light touch.

Since the PR aims to squash linting gremlins (trailing spaces and EOF newlines), I'm rolling with the assumption those cleanup hits are baked in here—but I can't spot 'em in the diff itself (they don't show in annotations). Before you pop the cork, drop a verification that your linting tool gives the all-clear. Also, take a quick eyeball at the rendered markdown locally to make sure these reflows don't throw off the visual hierarchy.

Also applies to: 34-35, 55-55

docs/janssen-server/auth-server/endpoints/ssa.md (1)

87-87: Solid linting fix, friend!

You better think twice... nah, I'm just messin' with ya! 🐦 This trailing whitespace trim is clean and pure—no content lost, just a little doc hygiene. The party's definitely rollin' now with this cleanup!

docs/janssen-server/auth-server/client-management/sector-identifiers.md (1)

11-16: Line reflow verified—formatting is correct with no trailing spaces and proper EOF newline.

The changes to lines 13–14 successfully reflow the paragraph about pairwise subject identifiers without altering content. Verification confirms:

  • ✓ No trailing spaces in the file
  • ✓ File ends with a newline

The documentation cleanup is complete and meets all linting standards.

docs/janssen-server/auth-server/endpoints/par.md (1)

12-18: The vibe is right on those editorial tweaks — formatting and line reflow looking good!

The markdown reflowing, line breaks, and wording adjustments throughout the doc keep things clear and readable. Nice work knocking out the trailing spaces and EOF newline cleanup. All the changes align with the linting objectives!

Also applies to: 48-53, 91-92, 95-95

docs/janssen-server/auth-server/authz-details/README.md (3)

46-48: You better think twice! 🕊️ Looks like there's still some cleanup work needed, my friend.

The static analysis caught trailing spaces on lines 46–47 (and possibly 52, 67), but from what I can see in the annotated code, they're marked as changed (~). If these lines have had their trailing spaces removed, that's the right move! However, if those trailing spaces are still lurking there like breadcrumbs on a park bench, they need to go. The linter is calling them out, and we gotta satisfy it.

Can you confirm that these lines no longer have trailing whitespace at the end?

Also applies to: 52-52, 67-67

174-181: Verify the EOF newline handling. 🕊️

Good vibes on tackling the end-of-file blank lines! I see lines 175–181 are marked as changed. The standard is to have exactly one newline character at the end of the file (which appears as a blank line in some editors).

Make sure the file now ends with the code block's closing fence (line 173), followed by one newline—no extra blank lines lingering. Can you confirm the EOF state is clean?

69-69: Link syntax looks solid! 🕊️

The relative link to the AuthzDetailType custom scripts on line 69 is structured correctly. Based on the project's documentation practices, these relative paths are tested and validated during the build. You're all set here!

docs/janssen-server/auth-server/endpoints/authorization-challenge.md (1)

1-789: Verify linting fixes are complete.

The PR claims to address trailing spaces and EOF newlines across documentation. This file still has static analysis warnings flagged above. Please confirm:

  1. Whether these linting issues are pre-existing or introduced by your changes
  2. Whether all markdown linting issues have been addressed (not just in this file, but across the PR)
  3. Ensure the file ends with a proper newline character

docs/contribute/implementation-design/jans-config-api-design/config-api-swagger-spec-generation.md (2)

1-246: Documentation structure and content look solid—let's get this party rollin'!

The markdown formatting is intact, links to GitHub repository resources are properly formatted, and the rewrapped lines (9-10, 31-32, 235-236) maintain the original meaning while improving readability. No syntax errors or broken references detected.

Once you confirm the linting tool gives it the green light, we're ready to roll!

9-10: Linting fixes incomplete—trailing spaces remain on multiple lines

The flagged lines (9-10, 31-32, 235-236) are now clean with no trailing spaces, and the file correctly ends with a newline. However, the file still contains trailing spaces on 16 other lines (16, 17, 18, 37, 38, 39, 40, 56, 57, 58, 101, 102, 103, 104, 144, 194). Either these lines were outside the PR's scope or the trailing space cleanup is incomplete. Please verify with your project's linting configuration and ensure all trailing spaces are removed before merging.

⛔ Skipped due to learnings 

Learnt from: pujavs
Repo: JanssenProject/jans PR: 12704
File: jans-config-api/docs/jans-config-api-swagger.yaml:17540-17546
Timestamp: 2025-11-18T07:43:55.761Z
Learning: The file `jans-config-api/docs/jans-config-api-swagger.yaml` is auto-generated with dependent modules changes and metadata. The config API does not override it.

docs/janssen-server/auth-server/endpoints/archived-jwks-uri.md (2)

12-14: Text reflow looks good—trailing spaces are gone!

The line joining and reflowing here aligns perfectly with the PR objective of cleaning up trailing whitespace. Nice work keeping the meaning intact.

45-45: MD031 violation claim is incorrect; "in the meantime" phrasing is standardized across endpoint docs.

Verification found that:

  1. MD031 is NOT violated: Both code fences (lines 20–22 and lines 26–28) are properly surrounded by blank lines—line 19 before the first fence, line 23 after it, line 25 before the second fence, and line 29 after it. Markdown linting requirements are met.
  2. "In the meantime" is standardized: This exact phrasing appears in at least 5 other endpoint documentation files (authorization.md, jwks-uri.md, par.md, userinfo.md), confirming it's part of a deliberate documentation pattern. Removing or modifying it here would break consistency across the documentation.

No actionable fixes are needed for this file.

docs/janssen-server/auth-server/endpoints/access-evaluation.md (2)

425-428: Confirm the EOF newline is in place.

Per the PR objectives about "ensuring end-of-file newlines," verify that there's a blank line after the closing code fence at line 428. The provided code view doesn't show trailing whitespace or the absolute end of the file.

12-24: Original review comment is incorrect - this is a new file creation, not a modification with scope mismatch.

The PR diff shows new file mode 100644 with 428 lines added (no deletions). This file didn't exist before, so there's no "substantial editorial rewording" of existing content—all text is being newly added.

The PR title "fix linting issues - trailing spaces and EOF newline" is misleading for a new file, but the review's claim of scope creep (content changes beyond linting fixes) doesn't apply when creating a file from scratch. The lines flagged (12–24, 41–42, 55–56, 62–73) are simply part of the initial content being introduced.

The real issue, if any, is that the PR title should reflect "add new documentation" rather than "fix linting issues." However, this is a titling accuracy problem, not the scope mismatch the review asserts.

docs/contribute/implementation-design/jans-cli-design/README.md (1)

11-11: Tighten up that contribution guidance! You better think twice about keeping redundant phrases.

The updated wording is more direct and professional. Dropping the "in the meantime" softener makes the call-to-action clearer without changing the core message—solid move for docs cleanup.

docs/contribute/implementation-design/jans-config-api-design/adr/README.md (1)

10-12: Nice line-reflow work, partner!

The documentation reads smoothly with these line breaks adjusted. This kind of markdown housekeeping keeps things clean and maintains consistent formatting across the documentation suite.

docs/contribute/implementation-design/jans-orm-design/adr/README.md (1)

10-12: Consistent formatting across the ADR docs—keep that party rollin'!

Same thoughtful line-reflow treatment as the other ADR READMEs. This shows a systematic and professional approach to documentation cleanup. Very nice!

docs/contribute/implementation-design/jans-casa-design/adr/README.md (1)

10-12: Same solid treatment as the rest of the ADR docs.

The line wrapping here maintains consistency with the documentation cleanup effort. Nothing fancy, just good housekeeping!

docs/janssen-server/auth-server/crypto/key-generation.md (1)

9-9: Trimmed that trailing space like a pro.

Removing trailing whitespace from the heading is exactly what linting cleanup should look like. Clean and simple!

docs/janssen-server/auth-server/logging/log4j2.md (1)

170-170: You better think twice before adding unnecessary phrases—this one's golden!

The rewording here directly addresses LanguageTool's suggestion about wordiness. Removing "in the meantime" makes the call-to-action punchier and more professional. Plus, it's consistent with the contribution guidance standardization across the docs. That's how you do linting cleanup right!

docs/janssen-server/auth-server/endpoints/README.md (1)

14-14: Smooth out that sentence—good editorial work!

Small wording refinement here makes the sentence read more naturally. These little clarity tweaks add up to better overall documentation quality.

docs/janssen-server/auth-server/international/client-config.md (1)

18-18: That's the right way to phrase the contribution call-to-action!

This follows the improved contribution guidance pattern seen across other docs in the PR. Clear, direct, and inviting. Perfect!

docs/janssen-server/auth-server/endpoints/session-revocation.md (1)

11-36: Lookin' good, friend! All the formatting cleanup here is spot-on—trailing space removal and line reflow enhance readability without touching the substance of the endpoint guidance. The content and links remain solid.

docs/janssen-server/auth-server/international/web-pages.md (1)

21-21: Smooth sailing here! The contribution text is now concise and direct—this standardization helps readers quickly understand how to get involved. The link is intact and ready to roll.

docs/contribute/implementation-design/jans-fido2-design/adr/README.md (1)

10-12: This one's clean! Line reflow improves consistency with documentation standards. The descriptive content about ADRs remains intact and crystal clear.

docs/janssen-server/auth-server/endpoints/token.md (1)

12-14: Excellent work on the polish! The line reflows across the token endpoint docs improve readability without touching the technical substance. All the critical endpoint info, configuration properties, and guidance remains rock-solid.

Also applies to: 17-18, 41-41, 128-128, 144-144

docs/contribute/implementation-design/jans-core-design/adr/README.md (1)

10-12: Looking sharp! Consistent line reflow across ADR READMEs. Content stays true to the original intent—documenting architectural decisions and design documentation. All good here.

docs/contribute/implementation-design/jans-cedarling-design/adr/README.md (1)

10-12: Right on! Consistent with the other ADR README line reflows. The message about ADRs and design documentation comes through loud and clear.

docs/janssen-server/auth-server/international/README.md (1)

13-13: Nicely done! The contribution text is now clearer and more direct. Switching from "document" to "page" and emphasizing "content" makes it easier for contributors to understand their role. The guidance is now consistent across the documentation.

docs/janssen-server/auth-server/logging/custom-logs.md (1)

11-13: Spot-on with the trailing whitespace cleanup here! The tweaks on lines 11 and 13 keep things tidy and linting-compliant.

docs/janssen-server/auth-server/international/scope-descriptions.md (1)

20-20: Editorial contribution guidance update looks good.

The wording refinement to the contributor invitation is consistent with the broader standardization effort across the documentation. The change improves clarity and directness.

docs/janssen-server/auth-server/endpoints/clientinfo.md (1)

54-54: Contributor guidance update is consistent with PR standardization.

The wording change aligns with the broader contributor guidance refinement across the documentation.

docs/janssen-server/auth-server/client-management/client-schema.md (1)

20-20: Contributor guidance update is consistent with documentation standardization.

The wording change follows the established pattern for refining contributor invitation language across the documentation set.

docs/contribute/implementation-design/jans-cli-design/adr/README.md (1)

10-12: ADR README formatting update is appropriate.

The text reflow improves readability while preserving the content and meaning.

docs/janssen-server/auth-server/logging/standard-logs.md (1)

26-26: Contributor guidance update maintains consistency across logging documentation.

The wording refinement aligns with the standardization effort applied throughout the documentation set.

docs/contribute/implementation-design/jans-core-design/README.md (1)

11-11: Contributor guidance wording refinement is consistent with broader documentation standardization.

The change follows the established pattern for updating contributor invitation language across the design documentation.

docs/janssen-server/auth-server/client-management/client-scripts.md (1)

20-20: Contributor guidance wording update aligns with documentation standardization.

The change is consistent with the contributor invitation refinements applied throughout the client-management documentation.

docs/janssen-server/auth-server/endpoints/end-session.md (1)

29-29: Based on my verification, I can now provide the rewritten review comment.

No trailing whitespace detected on line 29.

The examination of line 29 using cat -A (which displays trailing spaces as visible characters) shows the URL line ends immediately without any trailing spaces. The line contains only the URL text https://janssen.server.host/jans-auth/restv1/end_session followed by the line terminator, indicating this line does not violate MD009 linting rules.

Likely an incorrect or invalid review comment.

docs/janssen-server/auth-server/crypto/README.md (1)

14-14: You better think twice before leaving contributions on the table! ✓

The contribution guidance wording is now concise and aligned with the standardization across other docs pages. Nice work keeping it snappy!

docs/contribute/implementation-design/jans-scim-design/adr/README.md (1)

10-12: Line reflow for readability—nice touch!

The text wrapping here improves readability without changing the meaning. Documentation is cleaner now.

docs/contribute/implementation-design/jans-orm-design/README.md (1)

11-11: Standardized to the concise form—but watch for consistency!

The contribution guidance has been nicely shortened, removing the "in the meantime" phrase. However, this standardization is applied inconsistently across the PR: files like userinfo.md, jwks-uri.md, and authorization.md still retain the verbose form. Let's get this party rollin' by standardizing all contribution guidance text uniformly!

Check whether all "Want to contribute?" sections across the PR should use the concise form consistently.

docs/contribute/implementation-design/jans-scim-design/README.md (1)

11-11: Perfect—standardized contribution guidance! ✓

The concise form is in place and matches the standardization goal. This is the form all other "Want to contribute?" sections should adopt.

docs/janssen-server/auth-server/crypto/key-storage.md (1)

1021-1030: Documentation formatting improvements look solid.

The markdown bullet-point formatting and list restructuring maintain content clarity while improving readability. Trailing newline adjustments align with the PR's linting objectives.

docs/janssen-server/auth-server/endpoints/introspection.md (1)

13-19: Editorial refinements enhance documentation clarity.

The line rewraps and wording adjustments improve paragraph flow without altering technical content. The introspection scope distinction clarification (line 177) provides useful context for configuration.

Also applies to: 103-103, 177-177

docs/janssen-server/auth-server/logging/audit-logs.md (2)

19-23: JMS table formatting standardized nicely.

Removal of trailing spaces and single-line header formatting improves markdown consistency and linting compliance without affecting content readability.

25-42: Audit events list is well-structured.

The expanded event constants are clearly formatted and properly integrated. No issues detected.

docs/janssen-server/auth-server/client-management/client-authn.md (1)

12-14: Editorial refinements enhance documentation flow.

Wording adjustments throughout improve clarity and consistency. The rewording of authentication method descriptions and OpenID Connect references aligns well with best practices.

Also applies to: 19-19, 53-60, 99-104, 141-142, 159-160

docs/janssen-server/auth-server/crypto/keys.md (2)

10-11: Formatting improvements enhance readability.

Line breaks and spacing adjustments make the document more scannable without affecting content. Looks good!

177-182: Crypto algorithms documentation is well-organized.

The section rewording and table formatting improvements maintain clarity. Algorithm data and examples remain accurate.

Also applies to: 184-195, 199-201, 205-209, 221-226

docs/janssen-server/auth-server/client-management/README.md (1)

45-45: Whitespace cleanup looks good.

Trailing space removed as part of linting objectives. No functional impact.

docs/janssen-server/auth-server/endpoints/client-registration.md (1)

14-15: Editorial refinements improve documentation clarity throughout.

Numerous wording adjustments enhance readability and consistency. The rewording of client registration concepts, security pointers, and CRUD operation descriptions aligns with best practices.

Also applies to: 23-23, 47-48, 108-109, 137-138, 148-149, 163-164, 197-200, 205-206, 225-225, 569-570, 631-632, 647-648, 655-659, 670-672, 678-680

docs/janssen-server/auth-server/client-management/client-configuration.md (3)

56-58: Configuration endpoint references enhance navigation.

Adding well-known configuration endpoint references throughout improves document usability. Developers can now easily cross-reference supported algorithms and grant types.

Also applies to: 75-75, 89-89, 142-143

114-122: Grants table expansion provides valuable guidance.

The addition of Hybrid Flow, PKCE, Implicit Flow with Form Post, Device Flow, and Resource Owner Password Flow rows with their corresponding recommendations creates a more comprehensive grant type selection guide. This helps developers choose appropriate flows for their use cases.

100-100: Documentation improvements enhance clarity.

Rewording around grant type configuration, response_type defaults, and client expiration logic provides clearer guidance without altering functional meaning.

Also applies to: 151-152, 164-166