Skip to content

Commit cbb1348

Browse files
authored
Headings must start at the beginning of line fix (#37971)
1 parent b3fabc3 commit cbb1348

File tree

5 files changed

+5
-5
lines changed

5 files changed

+5
-5
lines changed

content/apps/publishing-apps-to-github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ You can add more information in the optional "Detailed description" field. You s
166166

167167
- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#headings) using Markdown. For example:
168168

169-
### Learn the skills you need
169+
### Learn the skills you need
170170

171171
{% data variables.product.prodname_learning %} can help you learn how to use {% data variables.product.company_short %}, communicate more effectively with Markdown, handle merge conflicts, and more.
172172

content/code-security/security-advisories/repository-security-advisories/evaluating-the-security-settings-of-a-repository.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ If you have admin permissions to the repository, and the repository is owned by
2222

2323
If a repository is private, you can only see the security settings if you have admin permissions to the repository or have been granted special security permissions covering the repository, for example, as an organization-wide security manager.
2424

25-
## Suggesting a security policy for a repository
25+
## Suggesting a security policy for a repository
2626

2727
If you do not have admin or security permissions for a public repository, you can still suggest a security policy to the repository maintainers if one doesn't already exist. The repository maintainers can then choose to accept or reject your suggestion. If the repository maintainers accept your suggestion, the security policy will be associated with the repository.
2828

content/get-started/quickstart/github-glossary.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ versions:
1212
ghec: '*'
1313
---
1414
{% for glossary in glossaries %}
15-
## {{ glossary.term }}
15+
## {{ glossary.term }}
1616
{{ glossary.description }}
1717

1818
{% endfor %}

content/site-policy/privacy-policies/github-privacy-statement.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ We share your personal data with service providers who process the information o
144144

145145
Such processing by service providers and any related cross border data transfers will be in compliance with applicable law.
146146

147-
### Affiliates
147+
### Affiliates
148148
We enable access to personal data across our subsidiaries, affiliates, and related companies, for example, where we share common data systems, when affiliates provide services on our behalf, or where access is needed to operate and provide the Service.
149149

150150
### For security purposes

data/reusables/enterprise_migrations/review-the-import-csv.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
To map authors from the original repository to an email address and name, create a new CSV file with the columns `ID,(ignored),GIT_EMAIL,GIT_NAME`, which replaces the author information for anything by "ID" with "GIT_EMAIL" and "GIT_NAME".
66

7-
#### Example:
7+
#### Example:
88

99
- Original author ID: `octocat@111111-2222-3333-4444-55555555555`
1010
- New email address: `octocat@github.com`

0 commit comments

Comments
 (0)