Fixed small deprecated link

Author: bbambozzi

src/content/9/en/part9b.md

@@ -788,7 +788,7 @@ We can also explicitly type things <i>any</i>. The only difference between impli
 Programmers however see the code differently when <i>any</i> is explicitly enforced than when it is implicitly inferred. 
 Implicit <i>any</i> typings are usually considered problematic, since it is quite often due to the coder forgetting to assign types (or being too lazy to do it), and it also means that the full power of TypeScript is not properly exploited. 
 
-This is why the configuration rule [noImplicitAny](https://www.typescriptlang.org/v2/en/tsconfig#noImplicitAny) exists on compiler level, and it is highly recommended to keep it on at all times. 
+This is why the configuration rule [noImplicitAny](https://www.typescriptlang.org/tsconfig#noImplicitAny) exists on compiler level, and it is highly recommended to keep it on at all times. 
 In the rare occasions when you truly cannot know what the type of a variable is, you should explicitly state that in the code:
 
 ```js