@@ -8,7 +8,7 @@ Change detection is sufficiently fast for most applications. However, when an ap
 
 OnPush is the default change detection strategy in Angular (since v22). It instructs Angular to run change detection for a component subtree **only** when:
 
-- The root component of the subtree receives new inputs as the result of a template binding. Angular compares the current and past value of the input with `==`.
+- The root component of the subtree receives new inputs as the result of a template binding. Angular compares the current and past value of the input with `Object.is`.
 - Angular handles an event _(for example using event binding, output binding, or `@HostListener` )_ in the subtree's root component or any of its children whether they are using OnPush change detection or not.
 
 ## Common change detection scenarios
 
@@ -2,7 +2,7 @@
 
 TIP: This guide assumes you're familiar with [component and directive outputs](guide/components/outputs).
 
-The `@angular/rxjs-interop` package offers two APIs related to component and directive outputs.
+The `@angular/core/rxjs-interop` package offers two APIs related to component and directive outputs.
 
 ## Creating an output based on an RxJs Observable
 
 
@@ -128,7 +128,7 @@ Here, only the last value (3) will be logged.
 
 ## Using `rxResource` for async data
 
-Angular's [`resource` function](/guide/signals/resource) gives you a way to incorporate async data into your application's signal-based code. Building on top of this pattern, `rxResource` lets you define a resource where the source of your data is defined in terms of an RxJS `Observable`. Instead of accepting a `loader` function, `rxResource` accepts a `stream` function that accepts an RxJS `Observable`.
+Angular's [`resource` function](/guide/signals/resource) gives you a way to incorporate async data into your application's signal-based code. Building on top of this pattern, `rxResource` lets you define a resource where the source of your data is defined in terms of an RxJS `Observable`. Instead of accepting a `loader` function, `rxResource` accepts a `stream` function that returns an RxJS `Observable`.
 
 ```typescript
 import {Component, inject} from '@angular/core';
 
@@ -14,15 +14,14 @@ The `SwUpdate` service supports three separate operations:
 
 ### Version updates
 
-The `versionUpdates` is an `Observable` property of `SwUpdate` and emits five event types:
-
-| Event types                      | Details                                                                                                                                                                               |
-| :------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `VersionDetectedEvent`           | Emitted when the service worker has detected a new version of the app on the server and is about to start downloading it.                                                             |
-| `NoNewVersionDetectedEvent`      | Emitted when the service worker has checked the version of the app on the server and did not find a new version.                                                                      |
-| `VersionReadyEvent`              | Emitted when a new version of the app is available to be activated by clients. It may be used to notify the user of an available update or prompt them to refresh the page.           |
-| `VersionInstallationFailedEvent` | Emitted when the installation of a new version failed. It may be used for logging/monitoring purposes.                                                                                |
-| `VersionFailedEvent`             | Emitted when a version encounters a critical failure (such as broken hash errors) that affects all clients using that version. Provides error details for debugging and transparency. |
+The `versionUpdates` is an `Observable` property of `SwUpdate` and emits four event types:
+
+| Event types                      | Details                                                                                                                                                                     |
+| :------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `VersionDetectedEvent`           | Emitted when the service worker has detected a new version of the app on the server and is about to start downloading it.                                                   |
+| `NoNewVersionDetectedEvent`      | Emitted when the service worker has checked the version of the app on the server and did not find a new version.                                                            |
+| `VersionReadyEvent`              | Emitted when a new version of the app is available to be activated by clients. It may be used to notify the user of an available update or prompt them to refresh the page. |
+| `VersionInstallationFailedEvent` | Emitted when the installation of a new version failed. It may be used for logging/monitoring purposes.                                                                      |
 
 <docs-code header="log-update.service.ts" path="adev/src/content/examples/service-worker-getting-started/src/app/log-update.service.ts" region="sw-update"/>
 
 
@@ -332,7 +332,7 @@ The ServiceWorker redirects navigation requests that don't match any `asset` or
 A request is considered to be a navigation request if:
 
 - Its [method](https://developer.mozilla.org/docs/Web/API/Request/method) is `GET`
-- Its [mode](https://developer.mozilla.org/docs/Web/API/Request/mode) is `navigation`
+- Its [mode](https://developer.mozilla.org/docs/Web/API/Request/mode) is `navigate`
 - It accepts a `text/html` response as determined by the value of the `Accept` header
 - Its URL matches the following criteria:
   - The URL must not contain a file extension (that is, a `.`) in the last path segment
 
@@ -18,7 +18,7 @@ import {Component, input} from '@angular/core';
     'aria-valuemax': '100',
 
     // Binding that updates the current value of the progressbar.
-    '[attr.aria-valuenow]': 'value',
+    '[attr.aria-valuenow]': 'value()',
   },
 })
 export class ExampleProgressbarComponent {
 
@@ -18,9 +18,6 @@ export class LogUpdateService {
         case 'VERSION_INSTALLATION_FAILED':
           console.log(`Failed to install app version '${evt.version.hash}': ${evt.error}`);
           break;
-        case 'VERSION_FAILED':
-          console.log(`Version '${evt.version.hash}' failed with error: ${evt.error}`);
-          break;
       }
     });
   }
 
@@ -45,4 +45,4 @@ import {Component, CUSTOM_ELEMENTS_SCHEMA} from '@angular/core';
 export class ComponentWithCustomElements { }
 ```
 
-Angular does not support any other schemas at this time.
+Angular also provides `NO_ERRORS_SCHEMA`, which allows any element and any property.
@@ -102,7 +102,7 @@ export class UserProfile {}
 
 If the query does not find a result, its value is `undefined`. This may occur if the target element is absent or hidden by `@if`. Angular keeps the result of `contentChild` up to date as your application state changes.
 
-By default, content queries find only _direct_ children of the component and do not traverse into descendants.
+By default, `contentChild` queries traverse into descendants, while `contentChildren` queries find only _direct_ children. See [Content descendants](#content-descendants).
 
 You can also query for multiple results with the `contentChildren` function.
 
 
@@ -135,7 +135,7 @@ Each component gets its own `UserClient` instance. Changes in one component don'
 **Solution:** Use `@Service` for singletons.
 
 ```ts {prefer, header: 'Root-level singleton'}
-import {Injectable} from '@angular/core';
+import {Service} from '@angular/core';
 
 @Service()
 export class UserClient {
@@ -250,7 +250,7 @@ export class UserProfile {
 Use `runInInjectionContext()` when you need to enable **other code** to call `inject()`. This is useful when accepting callbacks that might use dependency injection:
 
 ```angular-ts
-import {Component, inject, Injector, input} from '@angular/core';
+import {Component, inject, Injector, input, runInInjectionContext} from '@angular/core';
 
 @Component({
   selector: 'app-data-loader',
@@ -264,13 +264,13 @@ export class DataLoader {
     const callback = this.onLoad();
     if (callback) {
       // Enable the callback to use inject()
-      this.injector.runInInjectionContext(callback);
+      runInInjectionContext(this.injector, callback);
     }
   }
 }
 ```
 
-The `runInInjectionContext()` method creates a temporary injection context, allowing code inside the callback to call `inject()`.
+The `runInInjectionContext()` function creates a temporary injection context, allowing code inside the callback to call `inject()`.
 
 IMPORTANT: Always capture dependencies at the class level when possible. Use `injector.get()` for simple deferred retrieval, and `runInInjectionContext()` only when external code needs to call `inject()`.
 
@@ -671,7 +671,7 @@ This section provides detailed information about specific Angular DI error codes
 
 ### NullInjectorError: No provider for [Service]
 
-**Error code:** None (displayed as `NullInjectorError`)
+**Error code:** [NG0201](errors/NG0201)
 
 This error occurs when Angular cannot find a provider for a token in the injector hierarchy. The error message includes a dependency path showing where the injection was attempted.
 
@@ -855,12 +855,12 @@ Angular allows `inject()` in these locations:
    })
    export class UserProfile {
      private userService: UserClient;
+     user: ReturnType<UserClient['getUser']>;
 
      constructor() {
        this.userService = inject(UserClient); // Valid
+       this.user = this.userService.getUser();
      }
-
-     user = this.userService.getUser();
    }
    ```
 
@@ -882,7 +882,7 @@ Angular allows `inject()` in these locations:
 4. **Inside runInInjectionContext()**
 
    ```angular-ts
-   import {Component, inject, Injector} from '@angular/core';
+   import {Component, inject, Injector, runInInjectionContext} from '@angular/core';
    import {UserClient} from './user-client';
 
    @Component({
@@ -893,7 +893,7 @@ Angular allows `inject()` in these locations:
      private injector = inject(Injector);
 
      loadUser() {
-       this.injector.runInInjectionContext(() => {
+       runInInjectionContext(this.injector, () => {
          const userService = inject(UserClient); // Valid
          console.log(userService.getUser());
        });
@@ -934,7 +934,7 @@ private userService = inject(UserClient) // Capture at class level
 private injector = inject(Injector)
 
 someCallback() {
-  this.injector.runInInjectionContext(() => {
+  runInInjectionContext(this.injector, () => {
     const service = inject(MyClient)
   })
 }
Original file line number	Diff line number	Diff line change
`@@ -18,9 +18,6 @@ export class LogUpdateService {`
`18`	`18`	`case 'VERSION_INSTALLATION_FAILED':`
`19`	`19`	console.log(`Failed to install app version '${evt.version.hash}': ${evt.error}`);
`20`	`20`	`break;`
`21`		`- case 'VERSION_FAILED':`
`22`		- console.log(`Version '${evt.version.hash}' failed with error: ${evt.error}`);
`23`		`- break;`
`24`	`21`	`}`
`25`	`22`	`});`
`26`	`23`	`}`