From 14899d836dbf0b5886d0b91db5efb215d1aec1b4 Mon Sep 17 00:00:00 2001
From: RahulGautamSingh <rahultesnik@gmail.com>
Date: Thu, 4 Apr 2024 13:01:15 +0545
Subject: [PATCH] docs: typos and american spellings (#28215)

Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
---
 docs/usage/config-presets.md          |  2 +-
 docs/usage/configuration-options.md   | 12 ++++++------
 docs/usage/dependency-pinning.md      |  4 ++--
 docs/usage/examples/self-hosting.md   |  2 +-
 docs/usage/upgrade-best-practices.md  |  2 +-
 docs/usage/user-stories/swissquote.md |  2 +-
 lib/config/options/index.ts           |  4 ++--
 lib/modules/datasource/go/base.ts     |  2 +-
 lib/modules/manager/npm/utils.spec.ts |  2 +-
 lib/modules/platform/gitlab/index.ts  |  2 +-
 lib/modules/versioning/rez/pattern.ts |  2 +-
 tools/jest.mjs                        |  2 +-
 12 files changed, 19 insertions(+), 19 deletions(-)

diff --git a/docs/usage/config-presets.md b/docs/usage/config-presets.md
index b6b168c09e..9e05cd2f3a 100644
--- a/docs/usage/config-presets.md
+++ b/docs/usage/config-presets.md
@@ -165,7 +165,7 @@ Here is how you would use these in your Renovate config:
 In short, the number of `{{argx}}` parameters in the definition is how many parameters you need to provide.
 Parameters must be strings, non-quoted, and separated by commas if there are more than one.
 
-If you find that you are repeating config a lot, you might consider publishing one of these types of parameterised presets yourself.
+If you find that you are repeating config a lot, you might consider publishing one of these types of parameterized presets yourself.
 Or if you think your preset would be valuable for others, please contribute a PR to the Renovate repository, see [Contributing to presets](#contributing-to-presets).
 
 ## GitHub-hosted Presets
diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md
index b343f8d8d6..726a0c24f4 100644
--- a/docs/usage/configuration-options.md
+++ b/docs/usage/configuration-options.md
@@ -459,9 +459,9 @@ For example, To add `[skip ci]` to every commit you could configure:
 }
 ```
 
-Another example would be if you want to configure a DCO signoff to each commit.
+Another example would be if you want to configure a DCO sign off to each commit.
 
-If you want Renovate to signoff its commits, add the [`:gitSignOff` preset](./presets-default.md#gitsignoff) to your `extends` array:
+If you want Renovate to sign off its commits, add the [`:gitSignOff` preset](./presets-default.md#gitsignoff) to your `extends` array:
 
 ```json
 {
@@ -531,12 +531,12 @@ Composer `2.2` and up will be run with `--ignore-platform-req='ext-*' --ignore-p
 Older Composer versions will be run with `--ignore-platform-reqs`, which means that all platform constraints (including the PHP version) will be ignored by default.
 This can result in updated dependencies that are not compatible with your platform.
 
-To customize this behaviour, you can explicitly ignore platform requirements (for example `ext-zip`) by setting them separately in this array.
+To customize this behavior, you can explicitly ignore platform requirements (for example `ext-zip`) by setting them separately in this array.
 Each item will be added to the Composer command with `--ignore-platform-req`, resulting in it being ignored during its invocation.
 Note that this requires your project to use Composer V2, as V1 doesn't support excluding single platform requirements.
 The used PHP version will be guessed automatically from your `composer.json` definition, so `php` should not be added as explicit dependency.
 
-If an empty array is configured, Renovate uses its default behaviour.
+If an empty array is configured, Renovate uses its default behavior.
 
 Set to `null` (not recommended) to fully omit `--ignore-platform-reqs/--ignore-platform-req` during Composer invocation.
 This requires the Renovate image to be fully compatible with your Composer platform requirements in order for the Composer invocation to succeed, otherwise Renovate will fail to create the updated lock file.
@@ -1412,7 +1412,7 @@ For now, you can only use this option on the GitLab platform.
 
 For `followTag` to work, the datasource must support distribution streams or tags, like for example npm does.
 
-The main usecase is to follow a pre-release tag of a dependency, say TypeScripts's `"insiders"` build:
+The main use case is to follow a pre-release tag of a dependency, say TypeScripts's `"insiders"` build:
 
 ```json
 {
@@ -2165,7 +2165,7 @@ Consider this example:
 
 With the above config, every PR raised by Renovate will have the label `dependencies` while PRs containing `eslint`-related packages will instead have the label `linting`.
 
-Behaviour details:
+Behavior details:
 
 - On GitHub, GitLab and Gitea: Renovate will keep PR labels in sync with configured labels, provided that no other user or bot has made changes to the labels after PR creation. If labels are changed by any other account, Renovate will stop making further changes.
 - For other platforms, Renovate will add labels only at time of PR creation and not update them after that.
diff --git a/docs/usage/dependency-pinning.md b/docs/usage/dependency-pinning.md
index f001c127f2..2503bb40bf 100644
--- a/docs/usage/dependency-pinning.md
+++ b/docs/usage/dependency-pinning.md
@@ -6,7 +6,7 @@ description: The pros and cons of dependency pinning for JavaScript/npm
 # Should you Pin your JavaScript Dependencies?
 
 Once you start using a tool/service like Renovate, probably the biggest decision you need to make is whether to "pin" your dependencies instead of using SemVer ranges.
-The answer is "It's your choice", but we can certainly make some generalisations/recommendations to help you.
+The answer is "It's your choice", but we can certainly make some generalizations/recommendations to help you.
 
 If you don't want to read the in-depth discussion, you can skip ahead to our recommendations in the ["So what's best?" section](#so-whats-best).
 
@@ -72,7 +72,7 @@ By pinning dependencies you know exactly what you're running and you know exactl
 Now consider a similar theoretical scenario where `foobar@1.2.0` is faulty but it is _not_ caught by any of your automated tests.
 This is more common and more dangerous.
 
-If you were using SemVer ranges then this new version of `foobar` will likely be deployed to production automatically one day, sometime after which you notice errors and realise you need to fix it.
+If you were using SemVer ranges then this new version of `foobar` will likely be deployed to production automatically one day, sometime after which you notice errors and realize you need to fix it.
 Like before, you need to manually work out which dependency caused it - assuming you guess correctly that it was a new dependency version at fault - and pin it manually by editing `package.json` one dependency at a time.
 
 Alternatively, if you were instead pinning `foobar` then you would get a PR for `foobar@1.2.0` which awaits your approval.
diff --git a/docs/usage/examples/self-hosting.md b/docs/usage/examples/self-hosting.md
index 2d53114517..1e457fc670 100644
--- a/docs/usage/examples/self-hosting.md
+++ b/docs/usage/examples/self-hosting.md
@@ -384,7 +384,7 @@ spec:
 ## Logging
 
 If you're ingesting/parsing logs into another system then we recommend you set `LOG_LEVEL=debug` and `LOG_FORMAT=json` in your environment variables.
-Debug logging is usually needed for any debugging, while JSON format will mean that the output is parseable.
+Debug logging is usually needed for any debugging, while JSON format will mean that the output is parsable.
 
 ### About the log level numbers
 
diff --git a/docs/usage/upgrade-best-practices.md b/docs/usage/upgrade-best-practices.md
index f180921b86..9f95f0714a 100644
--- a/docs/usage/upgrade-best-practices.md
+++ b/docs/usage/upgrade-best-practices.md
@@ -80,7 +80,7 @@ The [GitHub Docs, using third-party actions](https://docs.github.com/en/actions/
 We recommend pinning _all_ Actions.
 That's why the `helpers:pinGitHubActionDigests` preset pins all GitHub Actions.
 
-For an in-depth explanation why you should pin your Github Actions, read the [Palo Alto Networks blogpost about the GitHub Actions worm](https://www.paloaltonetworks.com/blog/prisma-cloud/github-actions-worm-dependencies/).
+For an in-depth explanation why you should pin your Github Actions, read the [Palo Alto Networks blog post about the GitHub Actions worm](https://www.paloaltonetworks.com/blog/prisma-cloud/github-actions-worm-dependencies/).
 
 #### Extends `:pinDevDependencies`
 
diff --git a/docs/usage/user-stories/swissquote.md b/docs/usage/user-stories/swissquote.md
index e7f187f6bd..c11367f0cf 100644
--- a/docs/usage/user-stories/swissquote.md
+++ b/docs/usage/user-stories/swissquote.md
@@ -10,7 +10,7 @@
 > This article was originally published on [Medium](https://medium.com/swissquote-engineering/how-swissquote-is-keeping-software-dependencies-up-to-date-with-renovate-6246e8b20437) by [Stéphane Goetz](https://onigoetz.ch/), Principal Software Engineer at [Swissquote Bank](https://github.com/swissquote/).
 
 Swissquote has more than 1000 distinct applications running in production.
-They come in many different flavors including services, daemons, and webapps, and their age can be counted from days to more than a decade.
+They come in many different flavors including services, daemons, and web apps, and their age can be counted from days to more than a decade.
 While there are many topics of interest when talking about software maintenance, today’s topic is software dependencies.
 We’ll see in this article why it’s important to keep them up-to-date and why it’s not as simple as one may think.
 
diff --git a/lib/config/options/index.ts b/lib/config/options/index.ts
index 0932f04a07..d046fecc06 100644
--- a/lib/config/options/index.ts
+++ b/lib/config/options/index.ts
@@ -1578,7 +1578,7 @@ const options: RenovateOptions[] = [
     cli: false,
     env: false,
   },
-  // Version behaviour
+  // Version behavior
   {
     name: 'allowedVersions',
     description:
@@ -1840,7 +1840,7 @@ const options: RenovateOptions[] = [
     allowedValues: ['auto', 'never'],
     default: 'auto',
   },
-  // PR Behaviour
+  // PR Behavior
   {
     name: 'keepUpdatedLabel',
     description:
diff --git a/lib/modules/datasource/go/base.ts b/lib/modules/datasource/go/base.ts
index 3bde8e040f..f963490eeb 100644
--- a/lib/modules/datasource/go/base.ts
+++ b/lib/modules/datasource/go/base.ts
@@ -255,7 +255,7 @@ export class BaseGoDatasource {
     if (datasource !== null) {
       return datasource;
     }
-    // fall back to old behaviour if detection did not work
+    // fall back to old behavior if detection did not work
 
     switch (detectPlatform(goImportURL)) {
       case 'github': {
diff --git a/lib/modules/manager/npm/utils.spec.ts b/lib/modules/manager/npm/utils.spec.ts
index 039b520e8c..b154a83325 100644
--- a/lib/modules/manager/npm/utils.spec.ts
+++ b/lib/modules/manager/npm/utils.spec.ts
@@ -54,7 +54,7 @@ describe('modules/manager/npm/utils', () => {
       expect(lockFileComposed).toMatchSnapshot();
     });
 
-    it('adds trailing newline to match npms behaviour and avoid diffs', () => {
+    it('adds trailing newline to match npms behavior and avoid diffs', () => {
       const lockFile = Fixtures.get('lockfile-parsing/package-lock.json');
       const { detectedIndent, lockFileParsed } = parseLockFile(lockFile);
       // TODO #22198
diff --git a/lib/modules/platform/gitlab/index.ts b/lib/modules/platform/gitlab/index.ts
index 8f8b4debf4..e5b1e89368 100644
--- a/lib/modules/platform/gitlab/index.ts
+++ b/lib/modules/platform/gitlab/index.ts
@@ -267,7 +267,7 @@ function getRepoUrl(
     res.body.http_url_to_repo === null
   ) {
     if (res.body.http_url_to_repo === null) {
-      logger.debug('no http_url_to_repo found. Falling back to old behaviour.');
+      logger.debug('no http_url_to_repo found. Falling back to old behavior.');
     }
     if (process.env.GITLAB_IGNORE_REPO_URL) {
       logger.warn(
diff --git a/lib/modules/versioning/rez/pattern.ts b/lib/modules/versioning/rez/pattern.ts
index 8eac443ec6..96741017db 100644
--- a/lib/modules/versioning/rez/pattern.ts
+++ b/lib/modules/versioning/rez/pattern.ts
@@ -70,7 +70,7 @@ export const matchVersion = regEx(
 export const exactVersion = regEx(
   `^(?<exact_version>==(?<exact_version_group>${versionGroup})?)$`,
 ); /* Match an exact version number (e.g. ==1.0.0) */
-// inclusiveBound is called inclusive but behaviour in rez is this:
+// inclusiveBound is called inclusive but behavior in rez is this:
 // package-1..3 will match versions 1.2.3, 2.3.4, but not 3.0.0 or above
 export const inclusiveBound = regEx(
   `^(?<inclusive_bound>(?<inclusive_lower_version>${versionGroup})?\\.\\.(?<inclusive_upper_version>${versionGroup})?)$`,
diff --git a/tools/jest.mjs b/tools/jest.mjs
index 914cf82b36..9a2c8830eb 100644
--- a/tools/jest.mjs
+++ b/tools/jest.mjs
@@ -14,7 +14,7 @@ const args = ['--experimental-vm-modules'];
  * - #27375
  * - https://nodejs.org/en/blog/vulnerability/february-2024-security-releases#nodejs-is-vulnerable-to-the-marvin-attack-timing-variant-of-the-bleichenbacher-attack-against-pkcs1-v15-padding-cve-2023-46809---medium
  *
- * Sadly there is no way to suppress `SECURITY WARNING: Reverting CVE-2023-46809: Marvin attack on PKCS#1 padding` warining
+ * Sadly there is no way to suppress this warning: `SECURITY WARNING: Reverting CVE-2023-46809: Marvin attack on PKCS#1 padding`
  */
 if (semver.satisfies(version, '^18.19.1 || ^20.11.1 || >=21.6.2')) {
   args.push('--security-revert=CVE-2023-46809');
-- 
GitLab