Fix dead links

SMAKSS · SMAKSS · commit 4cceed89f6a3 · 2020-12-20T10:38:07.000+03:30
fixes microsoft#1400.
diff --git a/docs/Something Went Wrong.md b/docs/Something Went Wrong.md
@@ -26,6 +26,6 @@ The build to deploy train normally looks like this:
 
 You can deploy `v2` to production anytime via the ["Run workflow" button here](https://github.com/microsoft/TypeScript-Website/actions?query=workflow%3A%22Monday+Website+Push+To+Production%22), so if you have an emergency commit - it goes to `v2` then you can run the action.
 
-App Service apps are configured by [`Web.config`](https://github.com/microsoft/TypeScript-website/blob/92a9585d033e7cf802fae14v22baa73250fd610266/packages/typescriptlang-org/static/Web.config). [Here's a reference on the format](https://hangouts.google.com/call/H553wrJ9d97l2LMpNh9hAEEE). I've seen files (`*.json` & `*.manifest`) be 404s on the site because they were not in the config.
+App Service apps are configured by [`Web.config`](https://github.com/microsoft/TypeScript-website/blob/v2/packages/typescriptlang-org/static/Web.config). [Here's a reference on the format](https://hangouts.google.com/call/H553wrJ9d97l2LMpNh9hAEEE). I've seen files (`*.json` & `*.manifest`) be 404s on the site because they were not in the config.
 
 Check the build logs, they are always in [GitHub Actions](https://github.com/microsoft/TypeScript-Website/actions)
diff --git a/packages/create-typescript-playground-plugin/template/CONTRIBUTING.md b/packages/create-typescript-playground-plugin/template/CONTRIBUTING.md
@@ -12,7 +12,7 @@ Then set up the TypeScript playground to connect to a dev plugin at `http://loca
 
 #### Plugin API
 
-The plugin API is documented in the [interface PlaygroundPlugin in `./src/vendor/playground.d.ts`](src/vendor/playground.d.ts)
+The plugin API is documented in the [interface PlaygroundPlugin in `./src/index.ts`](src/index.ts).
 
 Roughly:
 
@@ -21,7 +21,7 @@ Roughly:
 
 ### Sandbox
 
-The plugins are passed copies of the TypeScript sandbox, which is a high level API wrapper to the [`monaco-editor`](https://microsoft.github.io/monaco-editor/). You can learn more about the sandbox on [the TypeScript website](http://www.typescriptlang.org/v2/dev/sandbox/
+The plugins are passed copies of the TypeScript sandbox, which is a high level API wrapper to the [`monaco-editor`](https://microsoft.github.io/monaco-editor/). You can learn more about the sandbox on [the TypeScript website](http://www.typescriptlang.org/v2/dev/sandbox/).
 
 #### Rollup
 
diff --git a/packages/documentation/copy/en/reference/Module Resolution.md b/packages/documentation/copy/en/reference/Module Resolution.md
@@ -213,13 +213,13 @@ Value of _baseUrl_ is determined as either:
 
 Note that relative module imports are not impacted by setting the baseUrl, as they are always resolved relative to their importing files.
 
-You can find more documentation on baseUrl in [RequireJS](http://requirejs.org/docs/api.html#config-baseUrl) and [SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/api.md#baseurl) documentation.
+You can find more documentation on baseUrl in [RequireJS](http://requirejs.org/docs/api.html#config-baseUrl) and [SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/api.md) documentation.
 
 ### Path mapping
 
 Sometimes modules are not directly located under _baseUrl_.
 For instance, an import to a module `"jquery"` would be translated at runtime to `"node_modules/jquery/dist/jquery.slim.min.js"`.
-Loaders use a mapping configuration to map module names to files at run-time, see [RequireJs documentation](http://requirejs.org/docs/api.html#config-paths) and [SystemJS documentation](https://github.com/systemjs/systemjs/blob/master/docs/config-api.md#paths).
+Loaders use a mapping configuration to map module names to files at run-time, see [RequireJs documentation](http://requirejs.org/docs/api.html#config-paths) and [SystemJS documentation](https://github.com/systemjs/systemjs/blob/master/docs/import-maps.md).
 
 The TypeScript compiler supports the declaration of such mappings using `"paths"` property in `tsconfig.json` files.
 Here is an example for how to specify the `"paths"` property for `jquery`.
diff --git a/packages/documentation/copy/en/reference/Modules.md b/packages/documentation/copy/en/reference/Modules.md
@@ -576,7 +576,7 @@ x(y);
 
 ### Wildcard module declarations
 
-Some module loaders such as [SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/overview.md#plugin-syntax)
+Some module loaders such as [SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/module-types.md)
 and [AMD](https://github.com/amdjs/amdjs-api/blob/master/LoaderPlugins.md) allow non-JavaScript content to be imported.
 These typically use a prefix or suffix to indicate the special loading semantics.
 Wildcard module declarations can be used to cover these cases.
diff --git a/packages/documentation/copy/en/release-notes/Overview.md b/packages/documentation/copy/en/release-notes/Overview.md
@@ -6671,7 +6671,7 @@ import A from "moduleA";
 ### Path mapping
 
 Sometimes modules are not directly located under _baseUrl_.
-Loaders use a mapping configuration to map module names to files at run-time, see [RequireJs documentation](http://requirejs.org/docs/api.html#config-paths) and [SystemJS documentation](https://github.com/systemjs/systemjs/blob/master/docs/overview.md#map-config).
+Loaders use a mapping configuration to map module names to files at run-time, see [RequireJs documentation](http://requirejs.org/docs/api.html#config-paths) and [SystemJS documentation](https://github.com/systemjs/systemjs/blob/master/docs/import-maps.md).
 
 The TypeScript compiler supports the declaration of such mappings using `"paths"` property in `tsconfig.json` files.
 
@@ -6754,7 +6754,7 @@ x(y);
 
 ## Wildcard character in module names
 
-Importing none-code resources using module loaders extension (e.g. [AMD](https://github.com/amdjs/amdjs-api/blob/master/LoaderPlugins.md) or [SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/creating-plugins.md)) has not been easy before;
+Importing none-code resources using module loaders extension (e.g. [AMD](https://github.com/amdjs/amdjs-api/blob/master/LoaderPlugins.md) or [SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/module-types.md)) has not been easy before;
 previously an ambient module declaration had to be defined for each resource.
 
 TypeScript 2.0 supports the use of the wildcard character (`*`) to declare a "family" of module names;
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 1.8.md b/packages/documentation/copy/en/release-notes/TypeScript 1.8.md
@@ -150,7 +150,7 @@ const Greeter = ({ name = "world" }) => <div>Hello, {name}!</div>;
 let example = <Greeter name="TypeScript 1.8" />;
 ```
 
-For this feature and simplified props, be sure to be use the [latest version of react.d.ts](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/react).
+For this feature and simplified props, be sure to be use the [latest version of react.d.ts](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/muicss/react.d.ts).
 
 ## Simplified `props` type management in React
 
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 2.0.md b/packages/documentation/copy/en/release-notes/TypeScript 2.0.md
@@ -544,7 +544,7 @@ import A from "moduleA";
 ## Path mapping
 
 Sometimes modules are not directly located under _baseUrl_.
-Loaders use a mapping configuration to map module names to files at run-time, see [RequireJs documentation](http://requirejs.org/docs/api.html#config-paths) and [SystemJS documentation](https://github.com/systemjs/systemjs/blob/master/docs/overview.md#map-config).
+Loaders use a mapping configuration to map module names to files at run-time, see [RequireJs documentation](http://requirejs.org/docs/api.html#config-paths) and [SystemJS documentation](https://github.com/systemjs/systemjs/blob/master/docs/import-maps.md).
 
 The TypeScript compiler supports the declaration of such mappings using `"paths"` property in `tsconfig.json` files.
 
@@ -627,7 +627,7 @@ x(y);
 
 ## Wildcard character in module names
 
-Importing none-code resources using module loaders extension (e.g. [AMD](https://github.com/amdjs/amdjs-api/blob/master/LoaderPlugins.md) or [SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/creating-plugins.md)) has not been easy before;
+Importing none-code resources using module loaders extension (e.g. [AMD](https://github.com/amdjs/amdjs-api/blob/master/LoaderPlugins.md) or [SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/module-types.md)) has not been easy before;
 previously an ambient module declaration had to be defined for each resource.
 
 TypeScript 2.0 supports the use of the wildcard character (`*`) to declare a "family" of module names;
diff --git a/packages/documentation/copy/en/release-notes/TypeScript 2.1.md b/packages/documentation/copy/en/release-notes/TypeScript 2.1.md
@@ -425,7 +425,7 @@ let v2 = c2; // Type "hello"
 
 In ES2015, constructors which return an object implicitly substitute the value of `this` for any callers of `super()`.
 As a result, it is necessary to capture any potential return value of `super()` and replace it with `this`.
-This change enables working with [Custom Elements](https://w3c.github.io/webcomponents/spec/custom/#htmlelement-constructor), which takes advantage of this to initialize browser-allocated elements with user-written constructors.
+This change enables working with [Custom Elements](https://www.w3.org/TR/custom-elements/), which takes advantage of this to initialize browser-allocated elements with user-written constructors.
 
 ##### Example
 
diff --git a/packages/documentation/copy/pt/reference/Module Resolution.md b/packages/documentation/copy/pt/reference/Module Resolution.md
@@ -213,13 +213,13 @@ O valor de _baseUrl_ &eacute; determinado como:
 
 Observe que as importa&ccedil;&otilde;es de m&oacute;dulos relativos n&atilde;o s&atilde;o afetadas pela configura&ccedil;&atilde;o de baseUrl, pois elas sempre s&atilde;o resolvidas em rela&ccedil;&atilde;o aos arquivos de importa&ccedil;&atilde;o.
 
-Voc&ecirc; pode encontrar mais documenta&ccedil;&atilde;o sobre baseUrl em [RequireJS](http://requirejs.org/docs/api.html#config-baseUrl) e [SystemJS](https://github.com/systemjs/systemjs/blob/master /docs/api.md#baseurl).
+Voc&ecirc; pode encontrar mais documenta&ccedil;&atilde;o sobre baseUrl em [RequireJS](http://requirejs.org/docs/api.html#config-baseUrl) e [SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/api.md).
 
 ### Mapeamento de caminhos
 
 &Agrave;s vezes, os m&oacute;dulos n&atilde;o est&atilde;o localizados diretamente em _baseUrl_.
 Por exemplo, uma importa&ccedil;&atilde;o para um m&oacute;dulo `"jquery"` seria traduzido em tempo de execu&ccedil;&atilde;o para `"node_modules/jquery/dist/jquery.slim.min.js"`.
-Os carregadores usam uma configura&ccedil;&atilde;o de mapeamento para mapear nomes de m&oacute;dulos para arquivos em tempo de execu&ccedil;&atilde;o, consulte a [documenta&ccedil;&atilde;o do RequireJs](http://requirejs.org/docs/api.html#config-paths) e a [documenta&ccedil;&atilde;o do SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/config-api.md#paths).
+Os carregadores usam uma configura&ccedil;&atilde;o de mapeamento para mapear nomes de m&oacute;dulos para arquivos em tempo de execu&ccedil;&atilde;o, consulte a [documenta&ccedil;&atilde;o do RequireJs](http://requirejs.org/docs/api.html#config-paths) e a [documenta&ccedil;&atilde;o do SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/import-maps.md).
 
 O compilador TypeScript suporta a declara&ccedil;&atilde;o de tais mapeamentos usando a propriedade `"paths"` nos arquivos `tsconfig.json`.
 Aqui est&aacute; um exemplo de como especificar a propriedade `"paths"` para `jquery`.

-Original file line number
+Diff line change
 Observe que as importações de módulos relativos não são afetadas pela configuração de baseUrl, pois elas sempre são resolvidas em relação aos arquivos de importação.
 -Você pode encontrar mais documentação sobre baseUrl em [RequireJS](http://requirejs.org/docs/api.html#config-baseUrl) e [SystemJS](https://github.com/systemjs/systemjs/blob/master /docs/api.md#baseurl).
 +Você pode encontrar mais documentação sobre baseUrl em [RequireJS](http://requirejs.org/docs/api.html#config-baseUrl) e [SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/api.md).
 ### Mapeamento de caminhos
 Às vezes, os módulos não estão localizados diretamente em _baseUrl_.
 Por exemplo, uma importação para um módulo `"jquery"` seria traduzido em tempo de execução para `"node_modules/jquery/dist/jquery.slim.min.js"`.
 -Os carregadores usam uma configuração de mapeamento para mapear nomes de módulos para arquivos em tempo de execução, consulte a [documentação do RequireJs](http://requirejs.org/docs/api.html#config-paths) e a [documentação do SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/config-api.md#paths).
 +Os carregadores usam uma configuração de mapeamento para mapear nomes de módulos para arquivos em tempo de execução, consulte a [documentação do RequireJs](http://requirejs.org/docs/api.html#config-paths) e a [documentação do SystemJS](https://github.com/systemjs/systemjs/blob/master/docs/import-maps.md).
 O compilador TypeScript suporta a declaração de tais mapeamentos usando a propriedade `"paths"` nos arquivos `tsconfig.json`.
 Aqui está um exemplo de como especificar a propriedade `"paths"` para `jquery`.