Doc review: Update Release 221121.7

[gladius-mtl]

No description provided.

[Platonn]

The imports and providers array might contain other customer's custom items. that's why in the original code snippet I added /*...*/.

[Platonn]

Suggested change

	Specifically, remove `provideClientHydration(withEventReplay(), withNoHttpTransferCache())` from the `providers` array. Your `app.module.ts` file should look as follows:
	```ts
	@NgModule({
	/* ... */
	providers: [
	/* ... */
	],
	})
	export class AppModule { }
	};
	```
	Specifically, remove `provideClientHydration(withEventReplay(), withNoHttpTransferCache())` from the `providers` array. Your `app.module.ts` file should look as follows:
	```ts
	@NgModule({
	/* ... */
	providers: [
	/* ... there should be no `provideClientHydration(withEventReplay(), withNoHttpTransferCache())` */
	],
	})
	export class AppModule { }
	};

[Platonn]

Suggested change

	Although not required, it is also recommended that you migrate your custom components to standalone components. For more information, see [Migrating to Standalone Components in Spartacus](standalone-components-in-spartacus.md).
	It is also strongly recommended that you migrate your custom components to standalone components. For more information, see [Migrating to Standalone Components in Spartacus](standalone-components-in-spartacus.md).

[Platonn]

If we left this separate doc, then only this sentence would remain, as we agreed offline.
I understand you decided to remove this doc alltoghether, because this sentence was too little to justify a separate doc for it. Works for me 👍

[Platonn]

The usage of v20 instead of v21 for angular-oauth2-oidc@20 might be confusing for customers. they might create support requests suggesting it's a typo.

What about adding a disclaimer that at the time of the release, the latest available version of angular-oauth2-oidc is v20, but the author of the library says it works also with Angular 21 as well. Source: manfredsteyer/angular-oauth2-oidc#1491 (comment)

[Platonn]

Suggested change

	Non-destructive hydration is an Angular feature that improves performance by reusing the server-rendered DOM instead of destroying and recreating it on the client side. This reduces the Time to Interactive (TTI) metric and provides a better user experience.
	Non-destructive hydration is an Angular feature that improves performance by reusing the server-rendered DOM instead of destroying and recreating it on the client side. This helps to avoid a flickering when transitioning from server-side DOM to client-side rendered DOM in the browser, which provides a better user experience.

[Platonn]

I'm sorry, I realized only now this paragraph is targeted to non-existing audience.

At this time or reading the document, customers' apps are likely not yet migrated to standalone. So I guess we can remove this paragraph and code snippet.

Only in the next section below ## Modernizing Your Storefront to Use the Standalone Bootstrap Application we'll tell customers to move this provideClientHydration() call from app.module.ts to app.config.ts.

[Platonn]

Suggested change

	After enabling hydration, you may see the following warning in your console:
	After enabling hydration, you may see the following warning in your console in dev-mode build:

[Platonn]

Suggested change

**Note:** The schematics to modernize your app only migrate your root `AppComponent` to become a standalone component. The schematics do not migrate your custom components to become standalone components. For more information about migrating your custom components, see [Standalone Components in Spartacus](#standalone-components-in-spartacus).

**Note:** The schematics to modernize your app only migrate your root `AppComponent` to become a standalone component. The schematics do not migrate your custom components to become standalone components. For more information about migrating your custom components, see [Standalone Components in Spartacus](#standalone-components-in-spartacus). But before migrating all your custom components to standalone, please follow the migration described here below.