docs: fix broken code fences and tag whitespace in ratelimit override pages#6253
Open
mintlify[bot] wants to merge 2 commits into
Open
docs: fix broken code fences and tag whitespace in ratelimit override pages#6253mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Repair structural markdown issues in the
@unkey/ratelimitSDK override reference pages so the code samples render correctly.Changes
libraries/ts/ratelimit/override/delete-override.mdx: replace straytscode blocks with proper closing/opening<RequestExample>.libraries/ts/ratelimit/override/get-override.mdx: same code-fence repair, plus remove the trailing space inside the</ResponseField >closing tag so the JSX tag is well-formed.Code samples themselves are left unchanged.
Context
A wider docs scan for spelling, grammar, and formatting issues was clean except for these two pages, where mismatched fence widths were swallowing the second example and the malformed closing tag was leaving
<ResponseField>unclosed in the parser.