From f337a8dfa11728a66ee8b98957b1e671825f71d8 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Sat, 10 May 2025 13:15:14 +0200 Subject: [PATCH] fix typos --- .../code-security/codeql-cli/codeql-cli-manual/resolve-ram.md | 2 +- ...roubleshooting-jekyll-build-errors-for-github-pages-sites.md | 2 +- content/rest/enterprise-admin/repo-pre-receive-hooks.md | 2 +- .../github-terms/github-sponsors-additional-terms.md | 2 +- .../jobs/setting-default-values-for-jobs-defaults-job-run.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/code-security/codeql-cli/codeql-cli-manual/resolve-ram.md b/content/code-security/codeql-cli/codeql-cli-manual/resolve-ram.md index 0c6ccabe1206..7bf63189c7cc 100644 --- a/content/code-security/codeql-cli/codeql-cli-manual/resolve-ram.md +++ b/content/code-security/codeql-cli/codeql-cli-manual/resolve-ram.md @@ -37,7 +37,7 @@ appropriate heuristics for deciding whether to keep some of the configured memory outside the Java heap. In particular, this should be used to find appropriate `-J-Xmx` and -`--off-heap-ram` options before staring a query server based on a +`--off-heap-ram` options before starting a query server based on a desired _total_ RAM amount. ## Options diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index c132d428b4c7..979b8a222d59 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -150,7 +150,7 @@ If you do want to use a submodule, initialize the submodule. For more informatio ## Relative permalinks configured -This errors means that you have relative permalinks, which are not supported by {% data variables.product.prodname_pages %}, in your `_config.yml` file. +This error means that you have relative permalinks, which are not supported by {% data variables.product.prodname_pages %}, in your `_config.yml` file. Permalinks are permanent URLs that reference a particular page on your site. Absolute permalinks begin with the root of the site, while relative permalinks begin with the folder containing the referenced page. {% data variables.product.prodname_pages %} and Jekyll no longer support relative permalinks. For more information about permalinks, see [Permalinks](https://jekyllrb.com/docs/permalinks/) in the Jekyll documentation. diff --git a/content/rest/enterprise-admin/repo-pre-receive-hooks.md b/content/rest/enterprise-admin/repo-pre-receive-hooks.md index cfb4f756e64e..bf46ed7b72a5 100644 --- a/content/rest/enterprise-admin/repo-pre-receive-hooks.md +++ b/content/rest/enterprise-admin/repo-pre-receive-hooks.md @@ -24,6 +24,6 @@ autogenerated: rest Possible values for _enforcement_ are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected. -`configuration_url` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level. +`configuration_url` may be a link to this repository, its organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level. diff --git a/content/site-policy/github-terms/github-sponsors-additional-terms.md b/content/site-policy/github-terms/github-sponsors-additional-terms.md index 3bfcd74e64c1..72570848d4f3 100644 --- a/content/site-policy/github-terms/github-sponsors-additional-terms.md +++ b/content/site-policy/github-terms/github-sponsors-additional-terms.md @@ -142,7 +142,7 @@ In the event of a Sponsored Developer's breach, or suspected breach, of these Ad During the term, GitHub will remit to you all Sponsored Developer Payments received in a given month within 30 days after the close of that month, subject to the variables below. Payouts are sent through Stripe Connect, ACH transfer, or wire transfer to the bank account you provided when you applied for GitHub Sponsors. We are not responsible for delay or misapplication of any Sponsored Developer Payment because of incorrect or incomplete information supplied by you or a bank, or for failure of a bank to credit your account. -* For first payments, GitHub will remit to you all Sponsored Developer Payments 60 days after the first sponsorship is initiated, subject to the variables below. This probation period is applied to all Sponsored Developer Accounts and helps insure the integrity of the program. Payments thereafter will be remitted within 30 days of the close of that month, in accordance with this section. +* For first payments, GitHub will remit to you all Sponsored Developer Payments 60 days after the first sponsorship is initiated, subject to the variables below. This probation period is applied to all Sponsored Developer Accounts and helps ensure the integrity of the program. Payments thereafter will be remitted within 30 days of the close of that month, in accordance with this section. * If you are paid through Stripe Connect, you will receive payouts on the 22nd of the month for the balance accrued since the last payout, regardless of the amount of the balance. Payout initiation dates vary by country, and can change from month to month due to public holidays, weekends, and other factors. When the payout is a cross-border payout, a minimum payout amount may apply. For more information, see [Receiving payouts](https://stripe.com/docs/payouts#cbp-minimum-payout-amounts) in the Stripe documentation. diff --git a/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md b/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md index 8d9c030e98cc..27807758a31a 100644 --- a/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md +++ b/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md @@ -2,6 +2,6 @@ Use `jobs..defaults.run` to provide default `shell` and `working-directo You can provide default `shell` and `working-directory` options for all [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) steps in a job. You can also set default settings for `run` for the entire workflow. For more information, see [`defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#defaultsrun). -These can be overriden at the `jobs..defaults.run` and `jobs..steps[*].run` levels. +These can be overridden at the `jobs..defaults.run` and `jobs..steps[*].run` levels. {% data reusables.actions.defaults-override %}