diff --git a/docs/development/local-development.md b/docs/development/local-development.md
index 8a74690e07529bb2b48d81d8416aef718bac51fc..fe9a54bb8dd2fff1a242686a2d00b29b4fd5faf6 100644
--- a/docs/development/local-development.md
+++ b/docs/development/local-development.md
@@ -38,7 +38,7 @@ You can also use [SDKMAN](https://sdkman.io/) to manage Java versions.
 #### Windows
 
 Follow these steps to set up your development environment on Windows 10.
-If you already installed a component, skip the corresponding step.
+If you already installed a part, skip the corresponding step.
 
 - Install [Git](https://git-scm.com/downloads). Make sure you've [configured your username and email](https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup)
 - Install [Node.js LTS](https://nodejs.org/en/download/)
diff --git a/lib/modules/versioning/regex/readme.md b/lib/modules/versioning/regex/readme.md
index bd6f40c4ed29c2b3f61a937279d4e129d6fc6b19..cabd8e88b08db6b0f4d56864246a6e36eec92272 100644
--- a/lib/modules/versioning/regex/readme.md
+++ b/lib/modules/versioning/regex/readme.md
@@ -4,7 +4,7 @@ The `regex` scheme makes use of Regular Express capture groups.
 The valid capture groups for `regex` versioning are:
 
 - `major`, `minor`, and `patch`: at least one of these must be provided. When determining whether a package has updates, these values will be compared in the standard semantic versioning fashion. If any of these fields are omitted, they will be treated as if they were `0` -- in this way, you can describe versioning schemes with up to three incrementing values.
-- `build`: this capture group can be used after you've already used the `major`, `minor` and `patch` capture groups and need a fourth version component. `build` updates are handled like `patch` updates.
+- `build`: this capture group can be used after you've already used the `major`, `minor` and `patch` capture groups and need a fourth version part. `build` updates are handled like `patch` updates.
 - `prerelease`: this value, if captured, will mark a given release as a prerelease (e.g. unstable). If this value is captured and you have configured `"ignoreUnstable": true`, the given release will be skipped.
 - `compatibility`: this value defines the "build compatibility" of a given dependency. A proposed Renovate update will never change the specified compatibility value. For example, if you are pinning to `1.2.3-linux` (and `linux` is captured as the compatibility value), Renovate will not update you to `1.2.4-osx`.