docs: Edits to remove jargon in Reference section (angular#42033)

PR Close angular#42033

Author: TeriGlover

aio/content/guide/architecture-components.md

@@ -3,7 +3,7 @@
 A *component* controls a patch of screen called a [*view*](guide/glossary#view "Definition of view").
 For example, individual components define and control each of the following views from the [Tour of Heroes tutorial](tutorial):
 
-* The app root with the navigation links.
+* The application root with the navigation links.
 * The list of heroes.
 * The hero editor.
 
@@ -17,7 +17,7 @@ The service is provided to the component through the dependency injection system
 
 <code-example path="architecture/src/app/hero-list.component.ts" header="src/app/hero-list.component.ts (class)" region="class"></code-example>
 
-Angular creates, updates, and destroys components as the user moves through the application. Your app can take action at each moment in this lifecycle through optional [lifecycle hooks](guide/lifecycle-hooks), like `ngOnInit()`.
+Angular creates, updates, and destroys components as the user moves through the application. Your application can take action at each moment in this lifecycle through optional [lifecycle hooks](guide/lifecycle-hooks), like `ngOnInit()`.
 
 ## Component metadata
 
@@ -35,7 +35,7 @@ Here's an example of basic metadata for `HeroListComponent`.
 
 This example shows some of the most useful `@Component` configuration options:
 
-* `selector`: A CSS selector that tells Angular to create and insert an instance of this component wherever it finds the corresponding tag in template HTML. For example, if an app's HTML contains `<app-hero-list></app-hero-list>`, then
+* `selector`: A CSS selector that tells Angular to create and insert an instance of this component wherever it finds the corresponding tag in template HTML. For example, if an application's HTML contains `<app-hero-list></app-hero-list>`, then
 Angular inserts an instance of the `HeroListComponent` view between those tags.
 
 * `templateUrl`: The module-relative address of this component's HTML template. Alternatively, you can provide the HTML template inline, as the value of the `template` property. This template defines the component's *host view*.
@@ -59,7 +59,7 @@ A view hierarchy can include views from components in the same NgModule, but it
 
 ## Template syntax
 
-A template looks like regular HTML, except that it also contains Angular [template syntax](guide/template-syntax), which alters the HTML based on your app's logic and the state of app and DOM data. Your template can use *data binding* to coordinate the app and DOM data, *pipes* to transform data before it is displayed, and *directives* to apply app logic to what gets displayed.
+A template looks like regular HTML, except that it also contains Angular [template syntax](guide/template-syntax), which alters the HTML based on your application's logic and the state of application and DOM data. Your template can use *data binding* to coordinate the application and DOM data, *pipes* to transform data before it is displayed, and *directives* to apply application logic to what gets displayed.
 
 For example, here is a template for the Tutorial's `HeroListComponent`.
 

aio/content/guide/architecture-modules.md

@@ -1,11 +1,11 @@
 # Introduction to modules
 
-Angular apps are modular and Angular has its own modularity system called *NgModules*.
+Angular applications are modular and Angular has its own modularity system called *NgModules*.
 NgModules are containers for a cohesive block of code dedicated to an application domain, a workflow, or a closely related set of capabilities. They can contain components, service providers, and other code files whose scope is defined by the containing NgModule. They can import functionality that is exported from other NgModules, and export selected functionality for use by other NgModules.
 
-Every Angular app has at least one NgModule class, [the *root module*](guide/bootstrapping), which is conventionally named `AppModule` and resides in a file named `app.module.ts`. You launch your app by *bootstrapping* the root NgModule.
+Every Angular application has at least one NgModule class, [the *root module*](guide/bootstrapping), which is conventionally named `AppModule` and resides in a file named `app.module.ts`. You launch your application by *bootstrapping* the root NgModule.
 
-While a small application might have only one NgModule, most apps have many more *feature modules*. The *root* NgModule for an app is so named because it can include child NgModules in a hierarchy of any depth.
+While a small application might have only one NgModule, most applications have many more *feature modules*. The *root* NgModule for an application is so named because it can include child NgModules in a hierarchy of any depth.
 
 ## NgModule metadata
 
@@ -17,9 +17,9 @@ An NgModule is defined by a class decorated with `@NgModule()`. The `@NgModule()
 
 * `imports`: Other modules whose exported classes are needed by component templates declared in *this* NgModule.
 
-* `providers`: Creators of [services](guide/architecture-services) that this NgModule contributes to the global collection of services; they become accessible in all parts of the app. (You can also specify providers at the component level.)
+* `providers`: Creators of [services](guide/architecture-services) that this NgModule contributes to the global collection of services; they become accessible in all parts of the application. (You can also specify providers at the component level.)
 
-* `bootstrap`: The main application view, called the *root component*, which hosts all other app views. Only the *root NgModule* should set the `bootstrap` property.
+* `bootstrap`: The main application view, called the *root component*, which hosts all other application views. Only the *root NgModule* should set the `bootstrap` property.
 
 Here's a simple root NgModule definition.
 
@@ -53,13 +53,13 @@ When you create a component, it's associated directly with a single view, called
 
 <div class="alert is-helpful">
 
-**Note:** The hierarchical structure of views is a key factor in the way Angular detects and responds to changes in the DOM and app data.
+**Note:** The hierarchical structure of views is a key factor in the way Angular detects and responds to changes in the DOM and application data.
 
 </div>
 
 ## NgModules and JavaScript modules
 
-The NgModule system is different from and unrelated to the JavaScript (ES2015) module system for managing collections of JavaScript objects. These are *complementary* module systems that you can use together to write your apps.
+The NgModule system is different from and unrelated to the JavaScript (ES2015) module system for managing collections of JavaScript objects. These are *complementary* module systems that you can use together to write your applications.
 
 In JavaScript each *file* is a module and all objects defined in the file belong to that module.
 The module declares some objects to be public by marking them with the `export` key word.

aio/content/guide/architecture-next-steps.md

@@ -15,15 +15,15 @@ about the features and tools that can help you develop and deliver Angular appli
 
 * The [NgModules](guide/ngmodules) guide provides in-depth information on the modular structure of an Angular application.
 
-* The [Routing and navigation](guide/router) guide provides in-depth information on how to construct applications that allow a user to navigate to different [views](guide/glossary#view) within your single-page app.
+* The [Routing and navigation](guide/router) guide provides in-depth information on how to construct applications that allow a user to navigate to different [views](guide/glossary#view) within your single-page application.
 
 * The [Dependency injection](guide/dependency-injection) guide provides in-depth information on how to construct an application such that each component class can acquire the services and objects it needs to perform its function.
 
 ## Responsive programming
 
 The [template syntax](guide/template-syntax) and related topics contain details about how to display your component data when and where you want it within a view, and how to collect input from users that you can respond to.
 
-Additional pages and sections describe some basic programming techniques for Angular apps.
+Additional pages and sections describe some basic programming techniques for Angular applications.
 
 * [Lifecycle hooks](guide/lifecycle-hooks): Tap into key moments in the lifetime of a component, from its creation to its destruction, by implementing the lifecycle hook interfaces.
 
@@ -38,13 +38,13 @@ without deep knowledge of animation techniques or CSS.
 
 ## Client-server interaction
 
-Angular provides a framework for single-page apps, where most of the logic and data resides on the client.
-Most apps still need to access a server using the `HttpClient` to access and save data.
+Angular provides a framework for single-page applications, where most of the logic and data resides on the client.
+Most applications still need to access a server using the `HttpClient` to access and save data.
 For some platforms and applications, you might also want to use the PWA (Progressive Web App) model to improve the user experience.
 
 * [HTTP](guide/http): Communicate with a server to get data, save data, and invoke server-side actions with an HTTP client.
 
-* [Server-side rendering](guide/universal): Angular Universal generates static application pages on the server through server-side rendering (SSR). This allows you to run your Angular app on the server in order to improve performance and show the first page quickly on mobile and low-powered devices, and also facilitate web crawlers.
+* [Server-side rendering](guide/universal): Angular Universal generates static application pages on the server through server-side rendering (SSR). This allows you to run your Angular application on the server in order to improve performance and show the first page quickly on mobile and low-powered devices, and also facilitate web crawlers.
 
 * [Service workers and PWA](guide/service-worker-intro): Use a service worker to reduce dependency on the network and significantly improve the user experience.
 
@@ -60,23 +60,23 @@ For some platforms and applications, you might also want to use the PWA (Progres
 
 * [Deployment](guide/deployment): Learn techniques for deploying your Angular application to a remote server.
 
-* [Security guidelines](guide/security): Learn about Angular's built-in protections against common web-app vulnerabilities and attacks such as cross-site scripting attacks.
+* [Security guidelines](guide/security): Learn about Angular's built-in protections against common web-application vulnerabilities and attacks such as cross-site scripting attacks.
 
-* [Internationalization](guide/i18n): Make your app available in multiple languages with Angular's internationalization (i18n) tools.
+* [Internationalization](guide/i18n): Make your application available in multiple languages with Angular's internationalization (i18n) tools.
 
-* [Accessibility](guide/accessibility): Make your app accessible to all users.
+* [Accessibility](guide/accessibility): Make your application accessible to all users.
 
 ## File structure, configuration, and dependencies
 
 * [Workspace and file structure](guide/file-structure): Understand the structure of Angular workspace and project folders.
 
 * [Building and serving](guide/build): Learn to define different build and proxy server configurations for your project, such as development, staging, and production.
 
-* [npm packages](guide/npm-packages): The Angular Framework, Angular CLI, and components used by Angular applications are packaged as [npm](https://docs.npmjs.com/) packages and distributed via the npm registry. The Angular CLI creates a default `package.json` file, which specifies a starter set of packages that work well together and jointly support many common application scenarios.
+* [npm packages](guide/npm-packages): The Angular Framework, Angular CLI, and components used by Angular applications are packaged as [npm](https://docs.npmjs.com/) packages and distributed using the npm registry. The Angular CLI creates a default `package.json` file, which specifies a starter set of packages that work well together and jointly support many common application scenarios.
 
 * [TypeScript configuration](guide/typescript-configuration): TypeScript is the primary language for Angular application development.
 
-* [Browser support](guide/browser-support): Make your apps compatible across a wide range of browsers.
+* [Browser support](guide/browser-support): Make your applications compatible across a wide range of browsers.
 
 ## Extending Angular
 

aio/content/guide/architecture-services.md

@@ -1,6 +1,6 @@
 # Introduction to services and dependency injection
 
-*Service* is a broad category encompassing any value, function, or feature that an app needs.
+*Service* is a broad category encompassing any value, function, or feature that an application needs.
 A service is typically a class with a narrow, well-defined purpose.
 It should do something specific and do it well.
 
@@ -17,7 +17,7 @@ A component can delegate certain tasks to services, such as fetching data from t
 validating user input, or logging directly to the console.
 By defining such processing tasks in an *injectable service class*, you make those tasks
 available to any component.
-You can also make your app more adaptable by injecting different providers of the same kind of service,
+You can also make your application more adaptable by injecting different providers of the same kind of service,
 as appropriate in different circumstances.
 
 Angular doesn't *enforce* these principles. Angular does help you *follow* these principles
@@ -50,7 +50,7 @@ Similarly, use the `@Injectable()` decorator to indicate that a component or oth
 
 * A *provider* is an object that tells an injector how to obtain or create a dependency.
 
-For any dependency that you need in your app, you must register a provider with the app's injector,
+For any dependency that you need in your app, you must register a provider with the application's injector,
 so that the injector can use the provider to create new instances.
 For a service, the provider is typically the service class itself.
 
@@ -93,7 +93,7 @@ or in the `@NgModule()` or `@Component()` metadata
  When you provide the service at the root level, Angular creates a single, shared instance of `HeroService`
  and injects it into any class that asks for it.
  Registering the provider in the `@Injectable()` metadata also allows Angular to optimize an app
- by removing the service from the compiled app if it isn't used, a process known as *tree-shaking*.
+ by removing the service from the compiled application if it isn't used, a process known as *tree-shaking*.
 
 * When you register a provider with a [specific NgModule](guide/architecture-modules), the same instance of a service is available to all components in that NgModule. To register at this level, use the `providers` property of the `@NgModule()` decorator.