Update wording to use "web-interop" instead of "web platform"

Author: eps1lon

docs/web-testing-library/intro.mdx

@@ -5,23 +5,20 @@ title: Introduction
 
 ## The problem
 
-You want to write maintainable tests for the
-[Web Platform](https://proposal-common-min-api.deno.dev/) or React Native. As a
-part of this goal, you want your tests to avoid including implementation details
-of your components and rather focus on making your tests give you the confidence
-for which they are intended. As part of this, you want your testbase to be
-maintainable in the long run so refactors of your components (changes to
-implementation but not functionality) don't break your tests and slow you and
-your team down.
+You want to write maintainable tests for [Web-interoperable
+runtimes][min-web-api]. As a part of this goal, you want your tests to avoid
+including implementation details of your components and rather focus on making
+your tests give you the confidence for which they are intended. As part of this,
+you want your testbase to be maintainable in the long run so refactors of your
+components (changes to implementation but not functionality) don't break your
+tests and slow you and your team down.
 
 ## This solution
 
 The `Web Testing Library` is a very light-weight solution for testing code that
-runs on the Web Platform (a browser, [Node.js][node], [Deno](https://deno.land/)
-etc) or React Native. The main utilities it provides involve querying the DOM
-for nodes in a way that's similar to how the user finds elements on the page. In
-this way, the library helps ensure your tests give you confidence in your UI
-code. The `DOM Testing Library`'s primary guiding principle is:
+runs on Web-interoperable runtimes (a browser, [Node.js][node], [Deno][deno]
+etc.) or [React Native][react-native]. The `Web Testing Library`'s primary
+guiding principle is:
 
 > The more your tests resemble the way your software is used, the more
 > confidence they can give you.
@@ -32,7 +29,7 @@ that closely resemble how your code is used on the Web Platform or React Native.
 Utilities are included in this project based on the following guiding
 principles:
 
-1. They should be usable on both the Web Platform **and** React Native
+1. They should be usable on the [minimum common web platform API][min-web-api]
 2. It should be generally useful for testing the application in the way the user
    would use it. We _are_ making some trade-offs here because we're using a
    computer and often a simulated environment, but in general, utilities should
@@ -47,3 +44,6 @@ principles:
 
 [jest]: https://jestjs.io
 [node]: https://nodejs.org/en/
+[deno]: https://deno.land/
+[react-native]: https://reactnative.dev/
+[min-web-api]: https://proposal-common-min-api.deno.dev/