Merge pull request #3583 from guymelef/patch-3

edit formatting

Author: mluukkai

src/content/9/en/part9b.md

@@ -304,9 +304,9 @@ Usually, types for existing packages can be found from the *@types* organization
 npm install --save-dev @types/react @types/express @types/lodash @types/jest @types/mongoose
 ```
 
-and so on and so on. The *@types/** are maintained by [Definitely typed](https://github.com/DefinitelyTyped/DefinitelyTyped), a community project to maintain types of everything in one place.
+and so on and so on. The *@types/* are maintained by [Definitely typed](https://github.com/DefinitelyTyped/DefinitelyTyped), a community project to maintain types of everything in one place.
 
-Sometimes, an npm package can also include its types within the code and, in that case, installing the corresponding *@types/** is not necessary.
+Sometimes, an npm package can also include its types within the code and, in that case, installing the corresponding *@types/* is not necessary.
 
 > **NB:** Since the typings are only used before compilation, the typings are not needed in the production build and they should *always* be in the devDependencies of the package.json.
 
@@ -318,7 +318,7 @@ Since version 10.0 *ts-node* has defined *@types/node* as a [peer dependency](ht
 npm install --save-dev @types/node
 ```
 
-When the package @types/node is installed, the compiler does not complain about the variable *process*. Note that there is no need to require the types to the code, the installation of the package is enough!
+When the package *@types/node* is installed, the compiler does not complain about the variable *process*. Note that there is no need to require the types to the code, the installation of the package is enough!
 
 ### Improving the project