docs(core): fixing some references to old architect terminology (#16424)

Co-authored-by: Isaac Mann <isaacplmann@gmail.com>

docs/generated/cli/run.md

@@ -1,11 +1,11 @@
 ---
 title: 'run - CLI command'
-description: 'Runs an Architect target with an optional custom builder configuration defined in your project.'
+description: 'Runs a target defined for your project. Target definitions can be found in the `scripts` property of the project `package.json`, or in the `targets` property of the project `project.json` file.'
 ---
 
 # run
 
-Runs an Architect target with an optional custom builder configuration defined in your project.
+Runs a target defined for your project. Target definitions can be found in the `scripts` property of the project `package.json`, or in the `targets` property of the project `project.json` file.
 
 ## Usage
 

docs/generated/packages/nest/documents/overview.md

@@ -93,7 +93,7 @@ nx build my-nest-lib
 
 #### Waiting for other builds
 
-Setting the `waitUntilTargets` option with an array of projects (with the following format: `"project:architect"`) will execute those commands before serving the Nest application.
+Setting the `waitUntilTargets` option with an array of projects (with the following format: `"project:target"`) will execute those commands before serving the Nest application.
 
 ### Serve
 

docs/generated/packages/node/documents/overview.md

@@ -76,7 +76,7 @@ nx g @nrwl/node:application my-new-app \
 
 ### Debugging
 
-Debugging is set to use a random port that is available on the system. The port can be changed by setting the port option in the `serve` architect in the project.json. Or by running the serve command with `--port <number>`.
+Debugging is set to use a random port that is available on the system. The port can be changed by setting the port option in the `serve` target in the project.json. Or by running the serve command with `--port <number>`.
 
 For additional information on how to debug Node applications, see the [Node.js debugging getting started guide](https://nodejs.org/en/docs/guides/debugging-getting-started/#inspector-clients).
 

docs/generated/packages/nx/documents/run.md

@@ -1,11 +1,11 @@
 ---
 title: 'run - CLI command'
-description: 'Runs an Architect target with an optional custom builder configuration defined in your project.'
+description: 'Runs a target defined for your project. Target definitions can be found in the `scripts` property of the project `package.json`, or in the `targets` property of the project `project.json` file.'
 ---
 
 # run
 
-Runs an Architect target with an optional custom builder configuration defined in your project.
+Runs a target defined for your project. Target definitions can be found in the `scripts` property of the project `package.json`, or in the `targets` property of the project `project.json` file.
 
 ## Usage
 

docs/shared/cli/run.md

@@ -1,11 +1,11 @@
 ---
 title: 'run - CLI command'
-description: 'Runs an Architect target with an optional custom builder configuration defined in your project.'
+description: 'Runs a target defined for your project. Target definitions can be found in the `scripts` property of the project `package.json`, or in the `targets` property of the project `project.json` file.'
 ---
 
 # run
 
-Runs an Architect target with an optional custom builder configuration defined in your project.
+Runs a target defined for your project. Target definitions can be found in the `scripts` property of the project `package.json`, or in the `targets` property of the project `project.json` file.
 
 ## Usage
 

docs/shared/core-features/integrate-with-editors.md

@@ -1,6 +1,6 @@
 # Integrate with Editors
 
-Nx Console is the UI for Nx. It works for any generator or any architect commands. Nx Console does not have a specific UI for, say, generating a component. Instead, Nx Console does what the command-line version of Nx does - it analyzes the same meta information to create the needed UI. This means that anything you can do with Nx, you can do with Nx Console.
+Nx Console is the UI for Nx. It works for any installed generators or any targets defined in your workspace. Nx Console does not have a specific UI for, say, generating a component. Instead, Nx Console does what the command-line version of Nx does - it analyzes the same meta information to create the needed UI. This means that anything you can do with Nx, you can do with Nx Console.
 
 ## Download
 

docs/shared/packages/nest/nest-plugin.md

@@ -93,7 +93,7 @@ nx build my-nest-lib
 
 #### Waiting for other builds
 
-Setting the `waitUntilTargets` option with an array of projects (with the following format: `"project:architect"`) will execute those commands before serving the Nest application.
+Setting the `waitUntilTargets` option with an array of projects (with the following format: `"project:target"`) will execute those commands before serving the Nest application.
 
 ### Serve
 

docs/shared/packages/node/node-plugin.md

@@ -76,7 +76,7 @@ nx g @nrwl/node:application my-new-app \
 
 ### Debugging
 
-Debugging is set to use a random port that is available on the system. The port can be changed by setting the port option in the `serve` architect in the project.json. Or by running the serve command with `--port <number>`.
+Debugging is set to use a random port that is available on the system. The port can be changed by setting the port option in the `serve` target in the project.json. Or by running the serve command with `--port <number>`.
 
 For additional information on how to debug Node applications, see the [Node.js debugging getting started guide](https://nodejs.org/en/docs/guides/debugging-getting-started/#inspector-clients).