docs: replace identify (#14709)

docs/development/creating-editing-renovate-presets.md

@@ -41,6 +41,6 @@ Rules:
 
 Rules:
 
-1. The primary use case of monorepo presets is identifying packages from the same origin source repository which should be updated together
+1. The primary use case of monorepo presets is finding packages from the same origin source repository which should be updated together
 1. Packages from the same repository which are developed and versioned independently do not need to be grouped as a monorepo, but in many cases we still do
 1. Packages from separate repositories but which are released together and dependent on each other may also be added to the "monorepo" definitions even if not strictly true

docs/development/issue-labeling.md

@@ -43,7 +43,7 @@ Most issues should have a label relating to either a platform, manager, datasour
 Use these to label the status of an issue.
 For example, use `status:requirements` to mean that an issue is not yet ready for development to begin.
 If we need the original poster or somebody else to respond to a query of ours, apply the `status:waiting-on-response` label.
-All open issues should have some `status:*` label applied, and [this search](https://github.com/renovatebot/renovate/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+-label%3Astatus%3Arequirements+-label%3Astatus%3Aready+-label%3Astatus%3Ain-progress+-label%3Astatus%3Ablocked+-label%3Astatus%3Awaiting-on-response+) can identify any which are missing a status label.
+All open issues should have some `status:*` label applied, and [this search](https://github.com/renovatebot/renovate/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+-label%3Astatus%3Arequirements+-label%3Astatus%3Aready+-label%3Astatus%3Ain-progress+-label%3Astatus%3Ablocked+-label%3Astatus%3Awaiting-on-response+) can find any which are missing a status label.
 
 ### Type of issue
 
@@ -63,7 +63,7 @@ For example, use `type:bug` to label a bug type issue, and use `type:feature` fo
 Only use `type:refactor` for code changes, don't use `type:refactor` for documentation type changes.
 Use the `type:help` label for issues which should be converted to a discussion post.
 
-Any issue which has the label `status:ready` should also have a `type:*` label, and [this search](https://github.com/renovatebot/renovate/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+-label%3Atype%3Abug+label%3Astatus%3Aready+-label%3Atype%3Afeature+-label%3Atype%3Adocs+-label%3Atype%3Arefactor+) can identify any which are missing one.
+Any issue which has the label `status:ready` should also have a `type:*` label, and [this search](https://github.com/renovatebot/renovate/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+-label%3Atype%3Abug+label%3Astatus%3Aready+-label%3Atype%3Afeature+-label%3Atype%3Adocs+-label%3Atype%3Arefactor+) can find any which are missing one.
 
 Add the `breaking` label for Issues or PRs which have changes that are not backwards compatible and require a major version bump.
 
@@ -198,4 +198,4 @@ Add a label `duplicate` to issues/PRs that are a duplicate of an earlier issue/P
 
 </details>
 
-Use the `self-hosted` label to identify when an issue is applicable only to users who self-administer their own bot.
+Apply the `self-hosted` label when an issue is applicable only to users who self-administer their own bot.

docs/usage/configuration-templates.md

@@ -41,7 +41,7 @@ Do not touch this unless you know what you're doing.
 You're probably fine leaving this setting alone, though you can change it.
 e.g. if you prefer that Renovate uses the term 'Upgrade' instead of 'Update' then you could configure `"commitMessageAction": "Upgrade"`.
 
-`commitMessageTopic` is usually two to three words that identify _what_ is being updated.
+`commitMessageTopic` is usually two to three words that show _what_ is being updated.
 e.g. it might be `dependency react` or `Docker image ubuntu`.
 You may want to edit this.
 If you think your new `commitMessageTopic` is helpful for others, please [open a PR](https://github.com/renovatebot/renovate/pulls).

docs/usage/getting-started/use-cases.md

@@ -61,7 +61,7 @@ If your dependencies are not detected by default, you can use use our "regex" ma
 You configure the regex manager by telling it:
 
 - Which file pattern(s) to match
-- How to identify the dependency name and version from within the file
+- How to find the dependency name and version from within the file
 - Which datasource (e.g. Docker registry, npm registry, etc) to use to look up new versions
 
 The end result is that Renovate can keep dependencies in custom file formats up-to-date as long as the dependency datasource is known to Renovate.