chore: drop store links

Author: kamilmysliwiec

content/controllers.md

@@ -512,8 +512,6 @@ export class AppModule {}
 
 We attached the metadata to the module class using the `@Module()` decorator, and Nest can now easily reflect which controllers have to be mounted.
 
-<app-banner-shop></app-banner-shop>
-
 #### Library-specific approach
 
 So far we've discussed the Nest standard way of manipulating responses. The second way of manipulating the response is to use a library-specific [response object](https://expressjs.com/en/api.html#res). In order to inject a particular response object, we need to use the `@Res()` decorator. To show the differences, let's rewrite the `CatsController` to the following:

content/fundamentals/dynamic-modules.md

@@ -67,7 +67,7 @@ The challenge is that the configuration module itself, since it's generic (simil
 
 In other words, dynamic modules provide an API for importing one module into another, and customizing the properties and behavior of that module when it is imported, as opposed to using the static bindings we've seen so far.
 
-<app-banner-shop></app-banner-shop>
+<app-banner-devtools></app-banner-devtools>
 
 #### Config module example
 
@@ -431,18 +431,17 @@ There are edge-cases when your module may need to take extra options that determ
 In such cases, the `ConfigurableModuleBuilder#setExtras` method can be used. See the following example:
 
 ```typescript
-export const { ConfigurableModuleClass, MODULE_OPTIONS_TOKEN } =
-  new ConfigurableModuleBuilder<ConfigModuleOptions>()
-    .setExtras(
-      {
-        isGlobal: true,
-      },
-      (definition, extras) => ({
-        ...definition,
-        global: extras.isGlobal,
-      }),
-    )
-    .build();
+export const { ConfigurableModuleClass, MODULE_OPTIONS_TOKEN } = new ConfigurableModuleBuilder<ConfigModuleOptions>()
+  .setExtras(
+    {
+      isGlobal: true,
+    },
+    (definition, extras) => ({
+      ...definition,
+      global: extras.isGlobal,
+    }),
+  )
+  .build();
 ```
 
 In the example above, the first argument passed into the `setExtras` method is an object containing default values for the "extra" properties. The second argument is a function that takes an auto-generated module definitions (with `provider`, `exports`, etc.) and `extras` object which represents extra properties (either specified by the consumer or defaults). The returned value of this function is a modified module definition. In this specific example, we're taking the `extras.isGlobal` property and assigning it to the `global` property of the module definition (which in turn determines whether a module is global or not, read more [here](/modules#dynamic-modules)).
@@ -466,9 +465,7 @@ However, since `isGlobal` is declared as an "extra" property, it won't be availa
 ```typescript
 @Injectable()
 export class ConfigService {
-  constructor(
-    @Inject(MODULE_OPTIONS_TOKEN) private options: ConfigModuleOptions,
-  ) {
+  constructor(@Inject(MODULE_OPTIONS_TOKEN) private options: ConfigModuleOptions) {
     // "options" object will not have the "isGlobal" property
     // ...
   }
@@ -482,11 +479,7 @@ The auto-generated static methods (`register`, `registerAsync`, etc.) can be ext
 ```typescript
 import { Module } from '@nestjs/common';
 import { ConfigService } from './config.service';
-import {
-  ConfigurableModuleClass,
-  ASYNC_OPTIONS_TYPE,
-  OPTIONS_TYPE,
-} from './config.module-definition';
+import { ConfigurableModuleClass, ASYNC_OPTIONS_TYPE, OPTIONS_TYPE } from './config.module-definition';
 
 @Module({
   providers: [ConfigService],
@@ -512,10 +505,5 @@ export class ConfigModule extends ConfigurableModuleClass {
 Note the use of `OPTIONS_TYPE` and `ASYNC_OPTIONS_TYPE` types that must be exported from the module definition file:
 
 ```typescript
-export const {
-  ConfigurableModuleClass,
-  MODULE_OPTIONS_TOKEN,
-  OPTIONS_TYPE,
-  ASYNC_OPTIONS_TYPE,
-} = new ConfigurableModuleBuilder<ConfigModuleOptions>().build();
+export const { ConfigurableModuleClass, MODULE_OPTIONS_TOKEN, OPTIONS_TYPE, ASYNC_OPTIONS_TYPE } = new ConfigurableModuleBuilder<ConfigModuleOptions>().build();
 ```

content/fundamentals/module-reference.md

@@ -231,4 +231,4 @@ export class CatsService {
 
 This technique enables you to conditionally instantiate different classes outside of the framework container.
 
-<app-banner-shop></app-banner-shop>
+<app-banner-devtools></app-banner-devtools>

content/graphql/resolvers-map.md

@@ -581,13 +581,12 @@ Assuming that we use the schema first approach and have enabled the typings gene
 
 ```typescript
 @@filename(graphql)
-export class Author {
+export (class Author {
   id: number;
   firstName?: string;
   lastName?: string;
   posts?: Post[];
-}
-
+})
 export class Post {
   id: number;
   title: string;
@@ -658,7 +657,7 @@ These arguments have the following meanings:
 - `info`: an object that contains information about the execution state of the query.
 - `args`: an object with the arguments passed into the field in the query.
 
-<app-banner-shop></app-banner-shop>
+<app-banner-devtools></app-banner-devtools>
 
 #### Module
 

content/microservices/basics.md

@@ -322,7 +322,7 @@ async publish() {
 
 The `emit()` method takes two arguments, `pattern` and `payload`. The `pattern`should match one defined in an `@EventPattern()` decorator. The `payload` is an event payload that we want to transmit to the remote microservice. This method returns a **hot `Observable`** (unlike the cold `Observable` returned by `send()`), which means that whether or not you explicitly subscribe to the observable, the proxy will immediately try to deliver the event.
 
-<app-banner-shop></app-banner-shop>
+<app-banner-devtools></app-banner-devtools>
 
 #### Scopes
 

content/openapi/migration-guide.md

@@ -35,4 +35,4 @@ The following methods have been added:
 - `addSecurity`
 - `addSecurityRequirements`
 
-<app-banner-shop></app-banner-shop>
+<app-banner-devtools></app-banner-devtools>

content/techniques/configuration.md

@@ -457,8 +457,6 @@ import { validate } from './env.validation';
 export class AppModule {}
 ```
 
-<app-banner-shop></app-banner-shop>
-
 #### Custom getter functions
 
 `ConfigService` defines a generic `get()` method to retrieve a configuration value by key. We may also add `getter` functions to enable a little more natural coding style:

src/app/homepage/menu/menu.component.ts

@@ -288,10 +288,10 @@ export class MenuComponent implements OnInit {
       isOpened: false,
       children: [{ title: 'Who is using Nest?', path: '/discover/companies' }],
     },
-    {
-      title: 'T-Shirts and Hoodies',
-      externalUrl: 'https://nestjs.threadless.com/',
-    },
+    // {
+    //   title: 'T-Shirts and Hoodies',
+    //   externalUrl: 'https://nestjs.threadless.com/',
+    // },
     {
       title: 'Support us',
       isOpened: false,