Skip to content

Commit 91976e6

Browse files
authored
Fix broken link to "Grammar and usage" brand guide page
1 parent 41e23c6 commit 91976e6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

contributing/content-style-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -336,7 +336,7 @@ When referencing text in the user interface, reproduce the text exactly. Use quo
336336
### More resources
337337
GitHub Brand Guide:
338338
- [Referring to GitHub features and product elements](https://brand.github.com/content/terminology/#referring-to-github-features-and-product-elements)
339-
- [Page names and UI references](https://brand.github.com/content/grammar-usage/#page-names-and-ui-references)
339+
- [Page names and UI references](https://brand.github.com/content/grammar#page-names-and-ui-references)
340340
Microsoft Style Guide:
341341
- [Formatting text in instructions](https://docs.microsoft.com/en-us/style-guide/procedures-instructions/formatting-text-in-instructions)
342342

@@ -346,7 +346,7 @@ Use clear, simple language that’s approachable and accessible for a wide range
346346

347347
## Word choice and terminology
348348

349-
For general guidance and GitHub-specific terms, see “[Terminology](https://brand.github.com/content/terminology) in and “[Words that can be tricky](https://brand.github.com/content/grammar-usage/#words-that-can-be-tricky)” in GitHub’s Brand Guide. For more detailed guidance, see the “[A-Z word list](https://docs.microsoft.com/en-us/style-guide)” in Microsoft’s style guide.
349+
For general guidance and GitHub-specific terms, see “[Terminology](https://brand.github.com/content/terminology) in and “[Words that can be tricky](https://brand.github.com/content/grammar#words-that-can-be-tricky)” in GitHub’s Brand Guide. For more detailed guidance, see the “[A-Z word list](https://docs.microsoft.com/en-us/style-guide)” in Microsoft’s style guide.
350350

351351
### Abbreviations
352352

0 commit comments

Comments
 (0)