[BUG] Fix Markdown formatting of non-consecutive headers: Open Data subchapter #1407
Closed
1 task done
Labels
bug
Something isn't working
good first issue
Good issue for newcomers to fix or respond to
Hacktoberfest
These issues or PRs maybe relevant for Hacktoberfest contributors.
jupytercon2020
This labels indicates issues and PRs interesting for the JupyterCon 2020 sprint attendees.
markdown
These issues or PR are related to a Markdown format file.
πππ° Welcome Hacktober Contributors! This is The Turing Way repository π°ππ
π«π₯βοΈ We're excited that you're here and want to contribute. βοΈπ₯π«
Summary of Issue
The Turing Way chapters are written in MarkDown format. Each chapter has a header (top-level header denoted by single # - h1 tag) and subheaders (## - h2, ### - h3, #### - h4 tags).
A standard expected format should follow
#
(h1 tag) ->##
(h2 tag) ->###
(h3 tag) and so on in sequence.What needs to be done
The Open Research's subchapters have non-consecutive header levels (instead of starting from h1, they start at h2, or some chapters have h1->h3, or h2->h4 instead of h1->h2->h3->h4 headers) which needs to be fixed.
Who can help
Anyone who would like to participate in Hacktoberfest or contribute to The Turing Way GitHub repository for the first time easier to do locally (by git) but not mandatory
About Hacktober and The Turing Way
Hacktoberfest is a month-long celebration of Open Source Projects where the goal is to make 4 Pull Requests during the month.
A bit about Git
If youβre new to git then here are some instructions to help you get going. Remember that you can ask us any questions you need to along the way.
A Pull Request (what Hacktober is measured on) lets you tell others about changes you've pushed to a branch in a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.
In this issue, weβve outlined what needs to be done, and how you can go about addressing it. Once the issue has been addressed, you can submit a Pull Request for review (tell us what youβve done) and we can incorporate it into The Turing Way.
Weβve also created this special Hacktoberfest tag to make it easy for you to find other places to contribute if youβre new.
In the spirit of Hacktoberfest, please only do a few of these to submit your PR so that we can learn and grow as a community together.
Our Community
We want to ensure that every user and contributor feel welcome, included, and supported to participate in The Turing Way community. We welcome all contributions to this project via GitHub issues and pull requests. Please read our Contributors document and our Code of Conduct while you engage in The Turing Way. As you start contributing to The Turing Way, don't forget that your ideas are more important than perfect pull requests. β€οΈ
If you have any questions that aren't discussed below, please let us know through one of the many ways to get in touch.
The text was updated successfully, but these errors were encountered: