Skip to content

Commit e9d6ca1

Browse files
authored
Merge pull request #51692 from github/repo-sync
Repo sync
2 parents b894984 + c3fe782 commit e9d6ca1

File tree

2 files changed

+2
-3
lines changed

2 files changed

+2
-3
lines changed

content/contributing/writing-for-github-docs/best-practices-for-github-docs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,15 +85,15 @@ For related information, see "Voice and tone" in [AUTOTITLE](/contributing/style
8585

8686
Most readers don't consume articles in their entirety. Instead they either _scan_ the page to locate specific information, or _skim_ the page to get a general idea of the concepts.
8787

88-
When scanning or skimming content, readers skip over large chunks of text. They look for elements that are related to their task or that stand out on the page, such as headings, callouts, lists, tables, code blocks, visuals, and the first few words in each section.
88+
When scanning or skimming content, readers skip over large chunks of text. They look for elements that are related to their task or that stand out on the page, such as headings, alerts, lists, tables, code blocks, visuals, and the first few words in each section.
8989

9090
Once the article has a clearly defined purpose and structure, you can apply the following formatting techniques to optimize the content for scanning and skimming. These techniques can also help to make content more understandable for all readers.
9191

9292
* **Use text highlighting** such as boldface and hyperlinks to call attention to the most important points. Use text highlighting sparingly. Do not highlight more than 10% of the total text in an article.
9393
* **Use formatting elements** to separate the content and create space on the page. For example:
9494
* Bulleted lists (with optional run-in subheads)
9595
* Numbered lists
96-
* [Callouts](/contributing/style-guide-and-content-model/style-guide#callouts)
96+
* [Alerts](/contributing/style-guide-and-content-model/style-guide#alerts)
9797
* Tables
9898
* Visuals
9999
* Code blocks and code annotations

data/reusables/gpg/copy-gpg-key-id.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
1. From the list of GPG keys, copy the long form of the GPG key ID you'd like to use. In this example, the GPG key ID is `3AA5C34371567BD2`:
22

33
```shell copy
4-
54
$ gpg --list-secret-keys --keyid-format=long
65
/Users/hubot/.gnupg/secring.gpg
76
------------------------------------

0 commit comments

Comments
 (0)