Merge pull request #130 from WebAssembly/mobile

Mention mobile platforms

2 files changed, 8 insertions, 5 deletions

diff --git a/HighLevelGoals.md b/HighLevelGoals.md
index 45c419c..93d8424 100644
--- a/HighLevelGoals.md
+++ b/HighLevelGoals.md
@@ -3,7 +3,8 @@
 1. Define a [portable](Portability.md), size- and load-time-efficient
    [binary format](MVP.md#binary-format) to serve as a compilation target which
    can be compiled to execute at native speed by taking advantage of common
-   hardware capabilities.
+   hardware capabilities available on a wide range of platforms, including
+   mobile and IoT™.
 2. Specify and implement incrementally:
     * design [a Minimum Viable Product (MVP)](MVP.md) for the standard with
       roughly the same functionality as [asm.js](http://asmjs.org);
diff --git a/MVP.md b/MVP.md
index cb9ec40..7b5602d 100644
--- a/MVP.md
+++ b/MVP.md
@@ -1,10 +1,12 @@
 # Minimum Viable Product
 
 As stated in the [high-level goals](HighLevelGoals.md), the first release aims
-at being a Minimum Viable Product (MVP), with roughly the same functionality as
-[asm.js](http://asmjs.org). This means that there are important features we
-*know* we want and need, but are post-MVP; these are in a separate [essential
-post-MVP features doc](EssentialPostMVPFeatures.md).
+at being a Minimum Viable Product (MVP). This means that there are important
+features we *know* we want and need, but are post-MVP; these are in a separate
+[essential post-MVP features doc](EssentialPostMVPFeatures.md). The MVP will
+contain features which are available today in modern web browsers and which
+perform well even on mobile devices, which leads to roughly the same
+functionality as [asm.js](http://asmjs.org).
 
 This document explains the contents of the MVP at a high-level. There are also
 separate docs with more precise descriptions of: