Merge branch 'nestjs:master' into master

Author: rubiin

LICENSE

@@ -1,6 +1,6 @@
 (The MIT License)
 
-Copyright (c) 2017-2022 Kamil Myśliwiec <http://kamilmysliwiec.com>
+Copyright (c) 2017-2023 Kamil Myśliwiec <http://kamilmysliwiec.com>
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

content/cli/libraries.md

@@ -19,7 +19,7 @@ Any functionality that is suitable for re-use is a candidate for being managed a
 To get started with creating a library, run the following command:
 
 ```bash
-nest g library my-library
+$ nest g library my-library
 ```
 
 When you run the command, the `library` schematic prompts you for a prefix (AKA alias) for the library:
@@ -78,7 +78,7 @@ As with application-type projects, libraries each have their own `tsconfig.lib.j
 You can build the library with the CLI command:
 
 ```bash
-nest build my-library
+$ nest build my-library
 ```
 
 #### Using libraries

content/cli/workspaces.md

@@ -26,7 +26,7 @@ To enable monorepo mode, you start with a _standard mode_ structure, and add **p
 If we run:
 
 ```bash
-nest new my-project
+$ nest new my-project
 ```
 
 We've constructed a _standard mode_ structure, with a folder structure that looks like this:
@@ -49,8 +49,8 @@ We've constructed a _standard mode_ structure, with a folder structure that look
 We can convert this to a monorepo mode structure as follows:
 
 ```bash
-cd my-project
-nest generate app my-app
+$ cd my-project
+$ nest generate app my-app
 ```
 
 At this point, `nest` converts the existing structure to a **monorepo mode** structure. This results in a few important changes. The folder structure now looks like this:

content/faq/request-lifecycle.md

@@ -34,7 +34,7 @@ Interceptors, for the most part, follow the same pattern as guards, with one cat
 
 #### Pipes
 
-Pipes follow the standard global to controller to route bound sequence, with the same first in first out in regards to the `@usePipes()` parameters. However, at a route parameter level, if you have multiple pipes running, they will run in the order of the last parameter with a pipe to the first. This also applies to the route level and controller level pipes. For example, if we have the following controller:
+Pipes follow the standard global to controller to route bound sequence, with the same first in first out in regards to the `@UsePipes()` parameters. However, at a route parameter level, if you have multiple pipes running, they will run in the order of the last parameter with a pipe to the first. This also applies to the route level and controller level pipes. For example, if we have the following controller:
 
 ```typescript
 @UsePipes(GeneralValidationPipe)