Fixed Note blockquote formatting in response examples in v1.0 topics#9904
Conversation
Corrected the formatting of the standard response example disclaimer — the "Note" sentence was inlined with the introductory sentence rather than rendered as a proper Markdown blockquote, reducing its visibility and breaking documentation formatting conventions.
There was a problem hiding this comment.
Pull request overview
Restores the "Note: The response object shown here might be shortened for readability." disclaimer as a proper Markdown blockquote on its own line in all response examples within a single v1.0 API reference topic. Previously the note was inlined with the preceding sentence so it rendered as plain text instead of a callout.
Changes:
- Splits the inlined response disclaimer into two lines across the eight response examples in
rangeformat-update.md. - Prefixes the disclaimer with
>so it renders as a blockquote, and bolds**Note:**.
|
Learn Build status updates of commit 08e9884: ✅ Validation status: passed
For more details, please refer to the build report. |
- Modified response sections across multiple API endpoints to clarify that the response object may be shortened for readability. - Ensured consistent formatting and phrasing in the response notes for improved user understanding.
|
Learn Build status updates of commit fed38d7:
|
|
Learn Build status updates of commit c686215:
|
|
Hi @Danipocket, this PR is also ready ;) |
Corrected the formatting of the standard response example disclaimer — the "Note" sentence was inlined with the introductory sentence rather than rendered as a proper Markdown blockquote, reducing its visibility and breaking documentation formatting conventions.