Merge pull request #2622 from Lioness100/master

docs: fix typos

Author: kamilmysliwiec

content/faq/serverless.md

@@ -172,7 +172,7 @@ Also, depending on whether you want to run a typical HTTP application with multi
 your application's code will look different (for example, for the endpoint-per-function approach you could use the `NestFactory.createApplicationContext` instead of booting the HTTP server, setting up middleware, etc.).
 
 Just for illustration purposes, we'll integrate Nest (using `@nestjs/platform-express` and so spinning up the whole, fully functional HTTP router)
-with the [Serverless](https://www.serverless.com/) framework (in this case, targetting AWS Lambda). As we've mentioned earlier, your code will differ depending on the cloud provider you choose, and many other factors.
+with the [Serverless](https://www.serverless.com/) framework (in this case, targeting AWS Lambda). As we've mentioned earlier, your code will differ depending on the cloud provider you choose, and many other factors.
 
 First, let's install the required packages:
 

content/fundamentals/unit-testing.md

@@ -327,7 +327,7 @@ Each of the override method types, in turn, returns the `TestingModule` instance
 
 Also, sometimes you may want to provide a custom logger e.g. when the tests are run (for example, on a CI server). Use the `setLogger()` method and pass an object that fulfills the `LoggerService` interface to instruct the `TestModuleBuilder` how to log during tests (by default, only "error" logs will be logged to the console).
   
-> warning **Warning** The `@nestjs/core` package exposes unique provider tokens with the `APP_` prefix to help on define global enhancers. Those tokens cannot be overriden since they can represent multiple providers. Thus you can't use `.overrideProvider(APP_GUARD)` (and so on). If you want to override some global enhancer, follow [this workaround](https://github.com/nestjs/nest/issues/4053#issuecomment-585612462).
+> warning **Warning** The `@nestjs/core` package exposes unique provider tokens with the `APP_` prefix to help on define global enhancers. Those tokens cannot be overridden since they can represent multiple providers. Thus you can't use `.overrideProvider(APP_GUARD)` (and so on). If you want to override some global enhancer, follow [this workaround](https://github.com/nestjs/nest/issues/4053#issuecomment-585612462).
 
 The compiled module has several useful methods, as described in the following table:
 

content/graphql/federation.md

@@ -713,7 +713,7 @@ export class AppModule {}
 
 #### Federated example: Gateway
 
-The gateway requires a list of endpoints to be specified and it will auto-discover the corresponding schemas. Therefore the implementation of the gateway servce will remain the same for both code and schema first approaches.
+The gateway requires a list of endpoints to be specified and it will auto-discover the corresponding schemas. Therefore the implementation of the gateway service will remain the same for both code and schema first approaches.
 
 ```typescript
 import {

content/graphql/subscriptions.md

@@ -564,7 +564,7 @@ GraphQLModule.forRoot<MercuriusDriverConfig>({
 
 Checking whether the user is authenticated can be done inside the `verifyClient` callback function that you can specify in the `subscription` options.
 
-The `verifyClient` will receive the `info` object as a first argument which you can use to retrive the request's headers.
+The `verifyClient` will receive the `info` object as a first argument which you can use to retrieve the request's headers.
 
 ```typescript
 GraphQLModule.forRoot<MercuriusDriverConfig>({

content/microservices/custom-transport.md

@@ -103,7 +103,7 @@ Hello world!
 
 Which means that our method handler was properly executed.
 
-When using a `CustomTransportStrategy` with [Interceptors](/interceptors) the handlers are wrapped into RxJS streams. This means that you need to subscribe to them in order to excute the streams underlying logic (e.g. continue into the controller logic after an interceptor has been excuted).
+When using a `CustomTransportStrategy` with [Interceptors](/interceptors) the handlers are wrapped into RxJS streams. This means that you need to subscribe to them in order to execute the streams underlying logic (e.g. continue into the controller logic after an interceptor has been executed).
 
 An example of this can be seen below:
 
@@ -122,7 +122,7 @@ async listen(callback: () => void) {
 
 As we mentioned in the first section, you don't necessarily need to use the `@nestjs/microservices` package to create microservices, but if you decide to do so and you need to integrate a custom strategy, you will need to provide a "client" class too.
 
-> info **Hint** Again, implementing a fully-featured client class compatible with all `@nestjs/microservices` features (e.g., streaming) requires a good understading of communication techniques used by the framework. To learn more, check out this [article](https://dev.to/nestjs/part-4-basic-client-component-16f9).
+> info **Hint** Again, implementing a fully-featured client class compatible with all `@nestjs/microservices` features (e.g., streaming) requires a good understanding of communication techniques used by the framework. To learn more, check out this [article](https://dev.to/nestjs/part-4-basic-client-component-16f9).
 
 To communicate with an external service/emit & publish messages (or events) you can either use a library-specific SDK package, or implement a custom client class that extends the `ClientProxy`, as follows:
 

content/migration.md

@@ -62,7 +62,7 @@ app = moduleFixture.createNestApplication<NestExpressApplication>({
 
 #### Kafka message/event handlers
 
-Previously, Kafka message and event handlers were receiving payloads as wrapped Kafka messages with `key`, `value`, `headers`, and a few other properites. In v9, those payloads are automatically unwrapped and your handlers will only receive the `value` attribute's value. To retrieve the original Kafka message, you can use the `KafkaContext` object (read more [here](/microservices/kafka#context)).
+Previously, Kafka message and event handlers were receiving payloads as wrapped Kafka messages with `key`, `value`, `headers`, and a few other properties. In v9, those payloads are automatically unwrapped and your handlers will only receive the `value` attribute's value. To retrieve the original Kafka message, you can use the `KafkaContext` object (read more [here](/microservices/kafka#context)).
 
 ```typescript
 // Before

content/recipes/mikroorm.md

@@ -245,7 +245,7 @@ const storage = new AsyncLocalStorage<EntityManager>();
   imports: [
     MikroOrmModule.forRoot({
       // ...
-      registerRequestContext: false, // disable automatatic middleware
+      registerRequestContext: false, // disable automatic middleware
       context: () => storage.getStore(), // use our AsyncLocalStorage instance
     }),
   ],

content/techniques/file-upload.md

@@ -120,9 +120,9 @@ export abstract class FileValidator<TValidationOptions = Record<string, any>> {
 - `MaxFileSizeValidator` - Checks if a given file's size is less than the provided value (measured in `bytes`)
 - `FileTypeValidator` - Checks if a given file's mime-type matches the given value. 
 
-> warning **Warning** To verify file type, [FileTypeValidator](https://github.com/nestjs/nest/blob/master/packages/common/pipes/file/file-type.validator.ts) class uses the type as detected by multer. By default, multer derives file type from file extension on user's device. However, it does not check actual file contents. As files can be renamed to arbitraty extensions, consider using a custom implementation (like checking the file's [magic number](https://www.ibm.com/support/pages/what-magic-number)) if your app requires a safer solution.
+> warning **Warning** To verify file type, [FileTypeValidator](https://github.com/nestjs/nest/blob/master/packages/common/pipes/file/file-type.validator.ts) class uses the type as detected by multer. By default, multer derives file type from file extension on user's device. However, it does not check actual file contents. As files can be renamed to arbitrary extensions, consider using a custom implementation (like checking the file's [magic number](https://www.ibm.com/support/pages/what-magic-number)) if your app requires a safer solution.
 
-To understand how these can be used in conjunction with the beforementioned `FileParsePipe`, we'll use an altered snippet of the last presented example:
+To understand how these can be used in conjunction with the aforementioned `FileParsePipe`, we'll use an altered snippet of the last presented example:
 
 ```typescript
 @UploadedFile(

src/app/homepage/pages/cli/cli.module.ts

@@ -2,7 +2,7 @@ import { CommonModule } from '@angular/common';
 import { NgModule } from '@angular/core';
 import { RouterModule, Routes } from '@angular/router';
 import { SharedModule } from './../../../shared/shared.module';
-import { CliLibrariesComponent } from './libraries/libaries.component';
+import { CliLibrariesComponent } from './libraries/libraries.component';
 import { CliOverviewComponent } from './overview/overview.component';
 import { CliUsagesComponent } from './usages/usages.component';
 import { CliWorkspacesComponent } from './workspaces/workspaces.component';