change wasm links to new page, add dart2wasm readme link

Author: MaryaBelanger

src/content/interop/js-interop/index.md

@@ -35,7 +35,7 @@ check out the [Past JS interop][] page for a more in depth summary on past
 iterations.
 
 [recently]: https://medium.com/dartlang/dart-3-3-325bf2bf6c13
-[Wasm]: {{site.flutter-docs}}/platform-integration/web/wasm
+[Wasm]: /web/wasm
 [`package:web`]: {{site.pub-pkg}}/web
 [`dart:html`]: {{site.dart-api}}/dart-html/dart-html-library.html
 [`dart:svg`]: {{site.dart-api}}/dart-svg/dart-svg-library.html

src/content/interop/js-interop/js-types.md

@@ -4,7 +4,7 @@ description: Usage information about the core types in JS interop.
 ---
 
 Dart values and JS values belong to separate language domains. When compiling to
-Wasm, they execute in separate *runtimes* as well. As such, you should treat JS
+[Wasm][], they execute in separate *runtimes* as well. As such, you should treat JS
 values as foreign types. To provide Dart types for JS values,
 [`dart:js_interop`] exposes a set of types prefixed with `JS` called "JS types".
 These types are used to distinguish between Dart values and JS values at
@@ -90,7 +90,7 @@ Generally, the conversion table looks like the following:
 </div>
 
 :::warning
-Compiling to JavaScript vs Wasm can introduce inconsistencies in both
+Compiling to JavaScript vs [Wasm][] can introduce inconsistencies in both
 performance and semantics for conversions. Conversions may have different costs
 depending on the compiler, so prefer to only convert values if you need to.
 
@@ -233,7 +233,7 @@ error if the value returned was JS `null` or `undefined` to ensure soundness.
 
 :::warning
 There is a subtle inconsistency with regards to `undefined` between compiling to
-JS and Wasm. While compiling to JS *treats* `undefined` values as if they were
+JS and [Wasm][]. While compiling to JS *treats* `undefined` values as if they were
 Dart `null`, it doesn't actually *change* the value itself. If an interop member
 returns `undefined` and you pass that value back into JS, JS will see
 `undefined`, *not* `null`, when compiling to JS.
@@ -279,4 +279,5 @@ See [`toExternalReference`] and [`toDartObject`] to convert to and from an
 [`JSBoxedDartObject`]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-js_interop/JSBoxedDartObject-extension-type.html
 [`ExternalDartReference`]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-js_interop/ExternalDartReference-extension-type.html
 [`toExternalReference`]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-js_interop/ObjectToExternalDartReference/toExternalReference.html
-[`toDartObject`]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-js_interop/ExternalDartReferenceToObject/toDartObject.html
+[`toDartObject`]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-js_interop/ExternalDartReferenceToObject/toDartObject.html
+[Wasm]: /web/wasm

src/content/interop/js-interop/package-web.md

@@ -298,7 +298,7 @@ Do we have any other package migrations to show off here?
 {% endcomment -%}
 
 [`package:web`]: {{site.pub-pkg}}/web
-[Wasm]: {{site.repo.dart.sdk}}/blob/main/pkg/dart2wasm/README.md
+[Wasm]: /web/wasm
 [html]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-html/dart-html-library.html
 [svg]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-svg/dart-svg-library.html
 [`dart:js_interop`]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-js_interop/dart-js_interop-library.html

src/content/interop/js-interop/past-js-interop.md

@@ -4,7 +4,7 @@ description: Archive of past JS interop implementations.
 ---
 
 :::warning
-None of these legacy interop libraries are supported when compiling to Wasm.
+None of these legacy interop libraries are supported when compiling to [Wasm][].
 :::
 
 This page addresses previous iterations of JS interop for Dart that are
@@ -121,3 +121,4 @@ TODO: Link to `package:web` section
 [`dart:js_util`]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-js_util
 [`Function.toJS`]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-js_interop/FunctionToJSExportedDartFunction/toJS.html
 [`dart:js_interop_unsafe`]: {{site.dart-api}}/{{site.sdkInfo.channel}}/dart-js_interop_unsafe
+[Wasm]: /web/wasm

src/content/web/wasm.md

@@ -78,13 +78,15 @@ by following the temporary steps outlined here:
    Add a new file `site/main.dart.js` and fill it with the contents of
    this [`main.dart.js` sample](https://gist.github.com/mit-mit/0fcb1247a9444b0cadf611aa5fc6f32e).
 
-1. Serve the output: `dart pub global run ` [`dhttpd`]
+1. Serve the output: `dart pub global run dhttpd` ([docs][dhttpd])
 
-You can also check out this small example [here](https://github.com/mit-mit/sandbox).
+You can also try out this small example [here](https://github.com/mit-mit/sandbox).
+To learn more about Wasm compilation in Dart, check out the [README][].
 
 [WasmGC]: https://developer.chrome.com/blog/wasmgc/
 [Flutter]: {{site.flutter}}/wasm
 [`package:web`]: {{site.pub-pkg}}/web
 [`dart:js_interop`]: {{site.dart.api}}/{{site.dart.sdk.channel}}/dart-js_interop 
 [migrated]: /interop/js-interop/package-web/
-[`dhttpd`]: {{site.pub-pkg}}/dhttpd
+[dhttpd]: {{site.pub-pkg}}/dhttpd
+[README]: {{site.repo.dart.sdk}}/blob/main/pkg/dart2wasm/README.md