fix: revise link and improve information about topics in the contributing docs#34491
Conversation
…ting docs Signed-off-by: Christine <shecoder30@gmail.com>
Signed-off-by: Christine <shecoder30@gmail.com>
Signed-off-by: Christine <shecoder30@gmail.com>
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
fpt: Free, Pro, Team |
|
@CBID2 Thank you for opening this PR! ✨ While we wait for guidance on the Markdown error, I'll triage this for a writer to review the content you've added 💛 |
|
@CBID2 I made a few minor updates regarding a run-on sentence and changing the phrase "Here's an example" to "For example" per guidance from our writers 💛 I'll update the branch and get this merged once tests are passing 🍏 Thank you again for opening this PR! ✨ |
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
This PR changes the link in the first paragraph in The "About Topics" article as well as adding an example on how to arrange the titles in frontmatter. Doing this would help contributors gain a better idea of how to contribute to GitHub's documentation.
Closes:
Closes #34378
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
datadirectory.For content changes, I have completed the self-review checklist.