[DOC] Fix non-consecutive header level increase#7339
Closed
dnskr wants to merge 1 commit intoapache:masterfrom
Closed
[DOC] Fix non-consecutive header level increase#7339dnskr wants to merge 1 commit intoapache:masterfrom
dnskr wants to merge 1 commit intoapache:masterfrom
Conversation
Signed-off-by: dnskr <dnskrv88@gmail.com>
pan3793
approved these changes
Mar 2, 2026
Member
|
thanks, merged to master |
dnskr
added a commit
that referenced
this pull request
Mar 2, 2026
### Why are the changes needed? The changes fix the following warnings that are printed during the documentation building: ``` ./kyuubi/docs/connector/spark/kudu.md.rst:42: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ./kyuubi/docs/connector/spark/kudu.md.rst:46: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ./kyuubi/docs/connector/spark/kudu.md.rst:50: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ./kyuubi/docs/connector/spark/kudu.md.rst:56: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ./kyuubi/docs/connector/spark/kudu.md.rst:82: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ./kyuubi/docs/connector/spark/kudu.md.rst:103: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ./kyuubi/docs/connector/spark/kudu.md.rst:121: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ./kyuubi/docs/monitor/logging.md.rst:190: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ./kyuubi/docs/monitor/logging.md.rst:194: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ./kyuubi/docs/monitor/logging.md.rst:210: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ./kyuubi/docs/monitor/logging.md.rst:214: WARNING: Non-consecutive header level increase; H2 to H4 [myst.header] ``` ### How was this patch tested? Checked that there are no warnings anymore during the documentation build process and the pages look the same. ``` make html open _build/html/monitor/logging.html open _build/html/connector/spark/kudu.html ``` ### Was this patch authored or co-authored using generative AI tooling? No Closes #7339 from dnskr/doc-fix-non-consecutive-header-level-increase. Closes #7339 18fc95b [dnskr] [DOC] Fix non-consecutive header level increase Authored-by: dnskr <dnskrv88@gmail.com> Signed-off-by: Cheng Pan <chengpan@apache.org> (cherry picked from commit ba7e057) Signed-off-by: dnskr <dnskrv88@gmail.com>
Contributor
Author
|
Merged to branch-1.11 as well. |
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
2 participants
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.
Why are the changes needed?
The changes fix the following warnings that are printed during the documentation building:
How was this patch tested?
Checked that there are no warnings anymore during the documentation build process and the pages look the same.
Was this patch authored or co-authored using generative AI tooling?
No