Conversation
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
...getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
Outdated
Show resolved
Hide resolved
…ting-and-formatting-on-github/basic-writing-and-formatting-syntax.md
|
@henrebotha Thanks for the PR! I'll accept this one based mostly on the fact that we actually tend to refer to them internally as "callouts," and I keep forgetting what term I'm supposed to be searching for when I'm trying to look up something about them. |
|
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:
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Adding synonyms for "alerts" to make them easier to find by searching.
Check off the following: