Updated module-types links to module-linking links (WebAssembly#330)

docs/DesignPrinciples.md

@@ -228,8 +228,8 @@ aligning with them so that we'll be ready when they are.
 As another example, WASI's
 [witx](https://github.com/WebAssembly/WASI/blob/master/docs/witx.md)
 file format is designed to be a
-straightforward superset of the [module type
-proposal](https://github.com/WebAssembly/module-types/blob/master/proposals/module-types/Overview.md)'s
+straightforward superset of the [module linking
+proposal](https://github.com/WebAssembly/module-linking/blob/master/proposals/module-linking/Explainer.md)'s
 .wit format and the [annotations
 proposal](https://github.com/WebAssembly/annotations/)'s annotation
 syntax.
@@ -243,8 +243,8 @@ transparently. This can be used to adapt or attenuate the functionality
 of a WASI API without changing the code using it.
 
 In WASI, we envision interposition will primarily be configured
-through the mechanisms in the module types' [link-time virtualization
-](https://github.com/WebAssembly/module-types/blob/module-imports/proposals/module-types/Explainer.md#link-time-virtualization).
+through the mechanisms in the module linking' [link-time virtualization
+](https://github.com/WebAssembly/module-linking/blob/master/proposals/module-linking/Explainer.md#link-time-virtualization).
 Imports are resolved when a module is instantiated, which may happen
 during the runtime of a larger logical application, so we can support
 interposition of WASI APIs without defining them in terms of explicit

docs/witx.md

@@ -1,7 +1,7 @@
 # Know your `witx`
 
 The `witx` file format is an experimental format which is based on the
-[module types] text format (`wit`), (which is in turn based on the
+[module linking] text format (`wit`), (which is in turn based on the
 [wat format], which is based on [S-expressions]). It adds some features
 using the same syntax as [interface types], some features with syntax
 similar to [gc types], as well as a few special features of its own.
@@ -22,7 +22,7 @@ the goals here are to remain aligned with interface types and other relevant
 WebAssembly standards and proposals wherever practical, and to be an input 
 into the design process of interface types.
 
-[module types]: https://github.com/WebAssembly/module-types/blob/master/proposals/module-types/Overview.md
+[module linking]: https://github.com/WebAssembly/module-linking/blob/master/proposals/module-linking/Explainer.md
 [interface types]: https://github.com/WebAssembly/interface-types/blob/master/proposals/interface-types/Explainer.md
 [gc types]: https://github.com/WebAssembly/gc
 [wat format]: https://webassembly.github.io/spec/core/bikeshed/index.html#text-format%E2%91%A0