Merge pull request github#28494 from github/repo-sync

Repo sync

content/admin/monitoring-managing-and-updating-your-instance/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md

@@ -69,7 +69,7 @@ The time required to failover depends on how long it takes to manually promote t
       cat /data/user/common/uuid
       ```
 
-    - On the new primary, remove the UUIDs using `ghe-repl-teardown`. Please replace *`UUID`* with a UUID you retrieved in the previous step.
+    - On the new primary, remove the UUIDs using `ghe-repl-teardown`. Please replace `UUID` with a UUID you retrieved in the previous step.
 
       ```shell
       ghe-repl-teardown -u  UUID

content/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps.md

@@ -67,7 +67,7 @@ Name | Description
  `read:public_key`| List and view details for public keys.
 **`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the {% data variables.product.prodname_oauth_app %}. {% data variables.product.pat_generic_caps %}s will only be able to perform these actions on organization hooks created by a user.
 **`gist`** | Grants write access to gists.
-**`notifications`** | Grants: <br/>*read access to a user's notifications*<br/> mark as read access to threads <br/>*watch and unwatch access to a repository, and*<br/> read, write, and delete access to thread subscriptions.
+**`notifications`** | Grants: <br/>read access to a user's notifications<br/> mark as read access to threads <br/>watch and unwatch access to a repository, and<br/> read, write, and delete access to thread subscriptions.
 **`user`** | Grants read/write access to profile info only.  Note that this scope includes `user:email` and `user:follow`.
 &emsp;`read:user`| Grants access to read a user's profile data.
 &emsp;`user:email`| Grants read access to a user's email addresses.

content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md

@@ -101,7 +101,7 @@ You can configure a _secret_scanning.yml_ file to exclude directories from {% da
 
     **Notes:**
     - If there are more than 1,000 entries in `paths-ignore`, {% data variables.product.prodname_secret_scanning %} will only exclude the first 1,000 directories from scans.
-    - If *secret_scanning.yml* is larger than 1 MB, {% data variables.product.prodname_secret_scanning %} will ignore the entire file.
+    - If `secret_scanning.yml` is larger than 1 MB, {% data variables.product.prodname_secret_scanning %} will ignore the entire file.
 
     {% endnote %}
 

content/contributing/syntax-and-versioning-for-github-docs/changing-an-articles-title.md

@@ -51,7 +51,7 @@ Make sure to update the link to the file in its parent `index.md` file, which ge
 
 ### Inline links within other articles
 
-We link between articles in our documentation. We recommend searching for both the filename *and* title to find links to update.
+We link between articles in our documentation. We recommend searching for both the filename and title to find links to update.
 
 ### Links across {% data variables.product.prodname_dotcom %}
 

content/contributing/writing-for-github-docs/content-model.md

@@ -288,7 +288,7 @@ Troubleshooting content includes built-in errors we expect people to encounter,
 
 #### Known issues
 
-Known issues are a subset of troubleshooting content specifically designed to respond to bugs, UX/UI issues, and other product quirks that generate a high volume of support tickets. Where troubleshooting content can describe errors that people *might* encounter, known issues explain problems that people *will* encounter.
+Known issues are a subset of troubleshooting content specifically designed to respond to bugs, UX/UI issues, and other product quirks that generate a high volume of support tickets. Where troubleshooting content can describe errors that people might encounter, known issues explain problems that people will encounter.
 
 Like all troubleshooting content, known issues can be a section in an article or a standalone article. If a known issue applies to a specific article, document it in that article. If a known issue applies to a specific set of articles or conceptual grouping of features, or if a product or feature has multiple known issues that should be grouped together, create a dedicated "Known issues with NAME" article.
 

content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md

@@ -35,10 +35,10 @@ You can indicate emphasis with bold, italic, strikethrough, subscript, or supers
 | Style | Syntax | Keyboard shortcut | Example | Output |
 | --- | --- | --- | --- | --- |
 | Bold | `** **` or `__ __`| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | `**This is bold text**` | **This is bold text** |
-| Italic | `* *` or `_ _`     | <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | `_This text is italicized_` | *This text is italicized* |
+| Italic | `* *` or `_ _`     | <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | `_This text is italicized_` | _This text is italicized_ |
 | Strikethrough | `~~ ~~` | None | `~~This was mistaken text~~` | ~~This was mistaken text~~ |
 | Bold and nested italic | `** **` and `_ _` | None | `**This text is _extremely_ important**` | **This text is _extremely_ important** |
-| All bold and italic | `*** ***` | None | `***All this text is important***` | ***All this text is important*** |
+| All bold and italic | `*** ***` | None | `***All this text is important***` | ***All this text is important*** | <!-- markdownlint-disable-line emphasis-style -->
 | Subscript | `<sub> </sub>` | None | `This is a <sub>subscript</sub> text` | This is a <sub>subscript</sub> text |
 | Superscript | `<sup> </sup>` | None | `This is a <sup>superscript</sup> text` | This is a <sup>superscript</sup> text |
 

content/site-policy/content-removal-policies/github-private-information-removal-policy.md

@@ -82,7 +82,7 @@ These guidelines are designed to make the processing of requests to remove priva
 
 1. A working, clickable link to each file containing private information. (Note that we're not able to work from search results, examples, or screenshots.)
 1. Specific line numbers within each file containing the private information.
-1. A brief description of how each item you've identified poses a security risk to you or your organization. ***It is important that you provide an explanation of how the data poses a security risk beyond merely stating that it does.***
+1. A brief description of how each item you've identified poses a security risk to you or your organization. ***It is important that you provide an explanation of how the data poses a security risk beyond merely stating that it does.*** <!-- markdownlint-disable-line emphasis-style -->
 1. If you are a third party acting as an agent for an organization facing a security risk, include a statement that you have a legal right to act on behalf of that organization.
 1. OPTIONAL: Let us know if your request is particularly urgent, and why. We respond to all private information removal requests as quickly as possible. However, if this request is especially time-sensitive, such as a very recent credential exposure, please explain why.
 

content/site-policy/content-removal-policies/guide-to-submitting-a-dmca-counter-notice.md

@@ -20,50 +20,50 @@ As with all legal matters, it is always best to consult with a professional abou
 
 ## Before You Start
 
-***Tell the Truth.***
+***Tell the Truth.*** <!-- markdownlint-disable-line emphasis-style -->
 The DMCA requires that you swear to your counter notice _under penalty of perjury_. It is a federal crime to intentionally lie in a sworn declaration. (_See_ [U.S. Code, Title 18, Section 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Submitting false information could also result in civil liability—that is, you could get sued for money damages.
 
-***Investigate.***
+***Investigate.*** <!-- markdownlint-disable-line emphasis-style -->
 Submitting a DMCA counter notice can have real legal consequences. If the complaining party disagrees that their takedown notice was mistaken, they might decide to file a lawsuit against you to keep the content disabled. You should conduct a thorough investigation into the allegations made in the takedown notice and probably talk to a lawyer before submitting a counter notice.
 
-***You Must Have a Good Reason to Submit a Counter Notice.***
+***You Must Have a Good Reason to Submit a Counter Notice.*** <!-- markdownlint-disable-line emphasis-style -->
 In order to file a counter notice, you must have "a good faith belief that the material was removed or disabled as a result of mistake or misidentification of the material to be removed or disabled." ([U.S. Code, Title 17, Section 512(g)](https://www.copyright.gov/title17/92chap5.html#512).) Whether you decide to explain why you believe there was a mistake is up to you and your lawyer, but you _do_ need to identify a mistake before you submit a counter notice. In the past, we have received counter notices citing mistakes in the takedown notice such as: the complaining party doesn't have the copyright; I have a license; the code has been released under an open-source license that permits my use; or the complaint doesn't account for the fact that my use is protected by the fair-use doctrine. Of course, there could be other defects with the takedown notice.
 
-***Copyright Laws Are Complicated.***
+***Copyright Laws Are Complicated.*** <!-- markdownlint-disable-line emphasis-style -->
 Sometimes a takedown notice might allege infringement in a way that seems odd or indirect. Copyright laws are complicated and can lead to some unexpected results. In some cases a takedown notice might allege that your source code infringes because of what it can do after it is compiled and run. For example:
   - The notice may claim that your software is used to [circumvent access controls](https://www.copyright.gov/title17/92chap12.html) to copyrighted works.
   - [Sometimes](https://www.copyright.gov/docs/mgm/) distributing software can be copyright infringement, if you induce end users to use the software to infringe copyrighted works.
   - A copyright complaint might also be based on [non-literal copying](https://en.wikipedia.org/wiki/Substantial_similarity) of design elements in the software, rather than the source code itself — in other words, someone has sent a notice saying they think your _design_ looks too similar to theirs.
 
 These are just a few examples of the complexities of copyright law. Since there are many nuances to the law and some unsettled questions in these types of cases, it is especially important to get professional advice if the infringement allegations do not seem straightforward.
 
-***A Counter Notice Is A Legal Statement.***
+***A Counter Notice Is A Legal Statement.*** <!-- markdownlint-disable-line emphasis-style -->
 We require you to fill out all fields of a counter notice completely, because a counter notice is a legal statement — not just to us, but to the complaining party. As we mentioned above, if the complaining party wishes to keep the content disabled after receiving a counter notice, they will need to initiate a legal action seeking a court order to restrain you from engaging in infringing activity relating to the content on GitHub. In other words, you might get sued (and you consent to that in the counter notice).
 
-***Your Counter Notice Will Be Published.***
+***Your Counter Notice Will Be Published.*** <!-- markdownlint-disable-line emphasis-style -->
 As noted in our [DMCA Takedown Policy](/site-policy/content-removal-policies/dmca-takedown-policy#d-transparency), **after redacting personal information,** we publish all complete and actionable counter notices at <https://github.com/github/dmca>. Please also note that, although we will only publicly publish redacted notices, we may provide a complete unredacted copy of any notices we receive directly to any party whose rights would be affected by it. If you are concerned about your privacy, you may have a lawyer or other legal representative file the counter notice on your behalf.
 
-***GitHub Isn't The Judge.***
+***GitHub Isn't The Judge.*** <!-- markdownlint-disable-line emphasis-style -->
 GitHub exercises little discretion in this process other than determining whether the notices meet the minimum requirements of the DMCA. It is up to the parties (and their lawyers) to evaluate the merit of their claims, bearing in mind that notices must be made under penalty of perjury.
 
-***Additional Resources.***
+***Additional Resources.*** <!-- markdownlint-disable-line emphasis-style -->
 If you need additional help, there are many self-help resources online. Lumen has an informative set of guides on [copyright](https://www.lumendatabase.org/topics/5) and [DMCA safe harbor](https://www.lumendatabase.org/topics/14). If you are involved with an open-source project in need of legal advice, you can contact the [Software Freedom Law Center](https://www.softwarefreedom.org/about/contact/). And if you think you have a particularly challenging case, non-profit organizations such as the [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) may also be willing to help directly or refer you to a lawyer.
 
 ## Your Counter Notice Must...
 
 1. **Include the following statement: "I have read and understand GitHub's Guide to Filing a DMCA Counter Notice."**
 We won't refuse to process an otherwise complete counter notice if you don't include this statement; however, we will know that you haven't read these guidelines and may ask you to go back and do so.
 
-1. ***Identify the content that was disabled and the location where it appeared.***
+1. ***Identify the content that was disabled and the location where it appeared.*** <!-- markdownlint-disable-line emphasis-style -->
 The disabled content should have been identified by URL in the takedown notice. You simply need to copy the URL(s) that you want to challenge.
 
 1. **Provide your contact information.**
 Include your email address, name, telephone number, and physical address.
 
-1. ***Include the following statement: "I swear, under penalty of perjury, that I have a good-faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled."***
+1. ***Include the following statement: "I swear, under penalty of perjury, that I have a good-faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled."*** <!-- markdownlint-disable-line emphasis-style -->
 You may also choose to communicate the reasons why you believe there was a mistake or misidentification. If you think of your counter notice as a "note" to the complaining party, this is a chance to explain why they should not take the next step and file a lawsuit in response. This is yet another reason to work with a lawyer when submitting a counter notice.
 
-1. ***Include the following statement: "I consent to the jurisdiction of Federal District Court for the judicial district in which my address is located (if in the United States, otherwise the Northern District of California where GitHub is located), and I will accept service of process from the person who provided the DMCA notification or an agent of such person."***
+1. ***Include the following statement: "I consent to the jurisdiction of Federal District Court for the judicial district in which my address is located (if in the United States, otherwise the Northern District of California where GitHub is located), and I will accept service of process from the person who provided the DMCA notification or an agent of such person."*** <!-- markdownlint-disable-line emphasis-style -->
 
 1. **Include your physical or electronic signature.**