docs
docs copied to clipboard
Fix incorrect use of "backslashes"
Regular expressions should be surrounded by forward slashes, but this doc referred to them as both "forward slashes" and "backslashes" in different places.
This PR updates "backslashes" -> "forward slashes".
Why:
Closes https://github.com/github/docs/issues/23123
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:
- [x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
- [x] For content changes, I have completed the self-review checklist.
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.
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 that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data
directory will not show up in this table.
Content directory changes
You 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.
Source | Preview | Production | What Changed |
---|---|---|---|
search-github/github-code-search/understanding-github-code-search-syntax.md |
fpt ghec |
fpt ghec |
fpt: Free, Pro, Team ghec: GitHub Enterprise Cloud ghes: GitHub Enterprise Server ghae: GitHub AE
@atenni Thank you for opening a PR and linking it to your issue! ✨
I'll get this triaged for review! :zap:
@nickmccurdy No problem - done :)
My initial instinct is explicit is better than implicit – but given the audience and the fact that there is example code for this on the page I think your suggestion reads better.
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 :zap: