docs(migration-guide): minor tweaks to terminus migration guide

Author: kamilmysliwiec

content/migration.md

@@ -8,16 +8,6 @@ To learn more about the new features we've added in the v8, check out this [link
 The `HttpModule` exported from the `@nestjs/common` package has been deprecated and will be removed in the next major release.
 Instead, please use the `@nestjs/axios` package (otherwise, there are no API differences).
 
-#### Terminus
-
-##### HttpHealthIndicator
-
-`HttpHealthIndicator` requires `@nestjs/axios` to be installed as well as `HttpModule` to be imported. Otherwise, there are no API differences.
-
-##### TerminusModule.forRoot{Async}
-
-The deprecated `TerminusModule.forRootAsync` has been removed. To migrate, check out the `@nestjs/terminus` v7.x.x [upgrade guide](https://docs.nestjs.com/v7/migration-guide#terminus)
-
 #### gRPC strategy
 
 The original Node gRPC library (`grpc`) has been deprecated and will no longer receive feature updates.
@@ -32,20 +22,26 @@ To upgrade, make sure to install the latest version of the `nats` package (`npm
 
 ```typescript
 // Before
-const app = await NestFactory.createMicroservice<MicroserviceOptions>(AppModule, {
-  transport: Transport.NATS,
-  options: {
-    url: 'nats://localhost:4222',
+const app = await NestFactory.createMicroservice<MicroserviceOptions>(
+  AppModule,
+  {
+    transport: Transport.NATS,
+    options: {
+      url: 'nats://localhost:4222',
+    },
   },
-});
+);
 
 // Now
-const app = await NestFactory.createMicroservice<MicroserviceOptions>(AppModule, {
-  transport: Transport.NATS,
-  options: {
-    servers: ['nats://localhost:4222'],
+const app = await NestFactory.createMicroservice<MicroserviceOptions>(
+  AppModule,
+  {
+    transport: Transport.NATS,
+    options: {
+      servers: ['nats://localhost:4222'],
+    },
   },
-});
+);
 ```
 
 #### `@All()` decorator
@@ -62,7 +58,6 @@ Instead, simply use the `listen()` and `startAllMicroservices()` methods (they a
 The `@nestjs/platform-socket.io` package was upgraded to use the `[email protected]` version (Nest v7 was based on the `socket.io` v2).
 To learn more, check out these articles: [Socket.io 3 Release](https://socket.io/blog/socket-io-3-release/) and [Socket.io 4 Release](https://socket.io/blog/socket-io-4-release/).
 
-
 #### Logger breaking changes
 
 For better extensibility, we separated out the `Logger` and `ConsoleLogger` classes ([PR](https://github.com/nestjs/nest/pull/6221), learn more in the [Logging](/techniques/logger) chapter). If your application uses a custom logger class that extends the built-in `Logger`, you should update it to extend the `ConsoleLogger` now.
@@ -79,7 +74,6 @@ Now:
 export class MyLogger extends ConsoleLogger {}
 ```
 
-
 #### `@nestjs/config` package
 
 There was a minor breaking change in the `registerAs` function (typings), you can see what has changed in [this PR](https://github.com/nestjs/config/pull/173).
@@ -90,6 +84,10 @@ There might be some small differences in how your auto-generated schema file loo
 
 Also, all `HttpException` errors thrown from your resolvers will be now automatically mapped to the corresponding `ApolloError` instances, unless you set the `autoTransformHttpErrors` configuration property (in the options object you pass into the `GraphQLModule#forRoot()` method) to `false`.
 
+#### `@nestjs/terminus` package
+
+`HttpHealthIndicator` requires `@nestjs/axios` to be installed as well as `HttpModule` to be imported. Also, the deprecated `TerminusModule.forRootAsync` has been removed. To migrate, check out the `@nestjs/terminus` v7.x.x [upgrade guide](https://docs.nestjs.com/v7/migration-guide#terminus).
+
 #### RxJS
 
 Make sure to upgrade to the latest version of the `rxjs` package (v7).

src/app/homepage/pages/microservices/custom-transport/custom-transport.component.html

@@ -197,8 +197,8 @@ <h4 appAnchor id="message-serialization"><span>Message serialization</span></h4>
 <p>If you need to add some custom logic around the serialization of responses on the client side, you can use a custom class that extends the <code>ClientProxy</code> class or one of its child classes. For modifying successful requests you can override the <code>serializeResponse</code> method, and for modifying any errors that go through this client you can override the <code>serializeError</code> method. To make use of this custom class, you can pass the class itself to the <code>ClientsModule.register()</code> method using the <code>customClass</code> property. Below is an example of a custom <code>ClientProxy</code> that serializes each error into an <code>RpcException</code>.</p>
 
 <span class="filename">
-  {{ 'error-handling.proxy' | extension: app6d39c222a0bedd88c115e6126918ef05b8d10064.isJsActive }}
-<app-tabs #app6d39c222a0bedd88c115e6126918ef05b8d10064></app-tabs>
+  {{ 'error-handling.proxy' | extension: app6cfb1a7ffd89db0636851e47b45f946d1913a4ef.isJsActive }}
+<app-tabs #app6cfb1a7ffd89db0636851e47b45f946d1913a4ef></app-tabs>
 </span><pre><code class="language-typescript">
 import &#123; ClientTcp, RpcException &#125; from &#39;@nestjs/microservices&#39;;
 
@@ -210,8 +210,8 @@ <h4 appAnchor id="message-serialization"><span>Message serialization</span></h4>
 </code></pre><p>and then use it in the <code>ClientsModule</code> like so:</p>
 
 <span class="filename">
-  {{ 'app.module' | extension: app58713f1e88f57e0ba10a9f3a0fbda5dfee0f3b97.isJsActive }}
-<app-tabs #app58713f1e88f57e0ba10a9f3a0fbda5dfee0f3b97></app-tabs>
+  {{ 'app.module' | extension: appa6c68c9ced980f6c3b4d7063dcf2e7e304b20254.isJsActive }}
+<app-tabs #appa6c68c9ced980f6c3b4d7063dcf2e7e304b20254></app-tabs>
 </span><pre><code class="language-typescript">
 @Module(&#123;
   imports: [