Hack week 2025: fix remaining "list capitalization" warnings excluding site-policy (#53924)

Author: felicitymay

content/code-security/code-scanning/troubleshooting-code-scanning/resource-not-accessible.md

@@ -57,7 +57,7 @@ For more information about editing the {% data variables.product.prodname_codeql
 
 If the {% data variables.code-scanning.codeql_workflow %} still fails on a commit made on the default branch, you need to check:
 
-* whether {% data variables.product.prodname_dependabot %} authored the commit
-* whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
+* Whether {% data variables.product.prodname_dependabot %} authored the commit
+* Whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
 
 This type of merge commit is authored by {% data variables.product.prodname_dependabot %} and therefore, any workflows running on the commit will have read-only permissions. If you enabled {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} security updates or version updates on your repository, we recommend you avoid using the {% data variables.product.prodname_dependabot %} `@dependabot squash and merge` command. Instead, you can enable auto-merge for your repository. This means that pull requests will be automatically merged when all required reviews are met and status checks have passed. For more information about enabling auto-merge, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge).

content/code-security/code-scanning/troubleshooting-sarif-uploads/file-too-large.md

@@ -40,8 +40,8 @@ There are many potential causes of very large SARIF results files.
 
 Take a look at the results file that was rejected by {% data variables.product.prodname_code_scanning %} to see if:
 
-* the SARIF file was compressed using gzip
-* the compressed file is smaller than 10 MB
+* The SARIF file was compressed using gzip
+* The compressed file is smaller than 10 MB
 
 If the file wasn't compressed using gzip, try compressing the file before rerunning the upload process. If the compressed file is still too large, you need to configure the analysis to generate a smaller set of results.
 

content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md

@@ -282,7 +282,7 @@ For most package managers, you should define a value that will match the depende
 
 Use to ignore specific versions or ranges of versions. If you want to define a range, use the standard pattern for the package manager. For example:
 
-* npm: use `^1.0.0`
+* npm: use `^1.0.0` <!-- markdownlint-disable-line GHD034 -->
 * Bundler: use `~> 2.0`
 * Docker: use Ruby version syntax
 * NuGet: use `7.*`

content/packages/learn-github-packages/about-permissions-for-github-packages.md

@@ -19,7 +19,7 @@ The following {% data variables.product.prodname_registry %} registries support
 
 * {% data variables.product.prodname_container_registry %}
 {%- ifversion packages-npm-v2 %}
-* npm registry
+* npm registry <!-- markdownlint-disable-line GHD034 -->
 {%- endif %}
 {%- ifversion packages-nuget-v2 %}
 * NuGet registry
@@ -38,7 +38,7 @@ The following {% data variables.product.prodname_registry %} registries **only**
 * Docker registry (`docker.pkg.github.com`)
 {%- endif %}
 {%- ifversion packages-npm-v2 %}{% else %}
-* npm registry
+* npm registry <!-- markdownlint-disable-line GHD034 -->
 {%- endif %}
 * Apache Maven registry
 * Gradle registry

content/webhooks/using-webhooks/delivering-webhooks-to-private-systems.md

@@ -14,11 +14,11 @@ You may want to deliver {% data variables.product.company_short %} webhooks to p
 
 A reverse proxy is a web server that sits between a client and an application. The reverse proxy receives requests from the client and forwards them to the application. This ensures no direct communication occurs between clients on the internet and the underlying application. A variety of systems can serve a reverse proxy, including:
 
-* web servers, like [nginx](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/)
+* Web servers, like [nginx](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/)
 * API gateways
-* free, open-source overlay networks, like [OpenZiti](https://openziti.io)
-* commercial ingress management tools, like [ngrok](https://ngrok.com/partners/github)
-* free, open-source ingress management tools, like [zrok](https://zrok.io)
+* Free, open-source overlay networks, like [OpenZiti](https://openziti.io)
+* Commercial ingress management tools, like [ngrok](https://ngrok.com/partners/github)
+* Free, open-source ingress management tools, like [zrok](https://zrok.io)
 
 How you configure your reverse proxy varies based on the system you're using.
 

content/webhooks/using-webhooks/validating-webhook-deliveries.md

@@ -62,7 +62,7 @@ You can use the following `secret` and `payload` values to verify that your impl
 
 If your implementation is correct, the signatures that you generate should match the following signature values:
 
-* signature: `757107ea0eb2509fc211221cce984b8a37570b6d7586c22c46f4379c8b043e17`
+* signature: `757107ea0eb2509fc211221cce984b8a37570b6d7586c22c46f4379c8b043e17` <!-- markdownlint-disable-line GHD034 -->
 * X-Hub-Signature-256: `sha256=757107ea0eb2509fc211221cce984b8a37570b6d7586c22c46f4379c8b043e17`
 
 ### Examples
@@ -182,12 +182,12 @@ const webhooks = new Webhooks({
 const handleWebhook = async (req, res) => {
   const signature = req.headers["x-hub-signature-256"];
   const body = await req.text();
-  
+
   if (!(await webhooks.verify(body, signature))) {
     res.status(401).send("Unauthorized");
     return;
   }
-  
+
   // The rest of your logic here
 };
 ```

data/reusables/rest-api/about-api-versions.md

@@ -2,23 +2,23 @@ The {% data variables.product.product_name %} REST API is versioned. The API ver
 
 Any breaking changes will be released in a new API version. Breaking changes are changes that can potentially break an integration. Breaking changes include:
 
-* removing an entire operation
-* removing or renaming a parameter
-* removing or renaming a response field
-* adding a new required parameter
-* making a previously optional parameter required
-* changing the type of a parameter or response field
-* removing enum values
-* adding a new validation rule to an existing parameter
-* changing authentication or authorization requirements
+* Removing an entire operation
+* Removing or renaming a parameter
+* Removing or renaming a response field
+* Adding a new required parameter
+* Making a previously optional parameter required
+* Changing the type of a parameter or response field
+* Removing enum values
+* Adding a new validation rule to an existing parameter
+* Changing authentication or authorization requirements
 
 Any additive (non-breaking) changes will be available in all supported API versions. Additive changes are changes that should not break an integration. Additive changes include:
 
-* adding an operation
-* adding an optional parameter
-* adding an optional request header
-* adding a response field
-* adding a response header
-* adding enum values
+* Adding an operation
+* Adding an optional parameter
+* Adding an optional request header
+* Adding a response field
+* Adding a response header
+* Adding enum values
 
 When a new REST API version is released, the previous API version will be supported for at least 24 more months following the release of the new API version.

data/reusables/support/help_resources.md

@@ -1,7 +1,7 @@
 For questions, bug reports, and discussions about {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, and API development, explore the {% data reusables.support.prodname_support_forum_with_url %}. The discussions are moderated and maintained by {% data variables.product.company_short %} staff, and answered by the {% data variables.product.company_short %} community.
 
 Consider reaching out to [GitHub Support](https://support.github.com/) directly using the contact form for:
-* guaranteed response from {% data variables.product.product_name %} staff
-* support requests involving sensitive data or private concerns
-* feature requests
-* feedback about {% data variables.product.product_name %} products
+* Guaranteed response from {% data variables.product.product_name %} staff
+* Support requests involving sensitive data or private concerns
+* Feature requests
+* Feedback about {% data variables.product.product_name %} products