MarkDown edits (#348)

* typo: focused

* typo: typeidx

* high-ldevl UseCases: reword for clarity

* improve sentence structure with comma

* typo: goals

Author: FrankReh

README.md

@@ -1,6 +1,6 @@
 # Component Model design and specification
 
-This repository is where the component model is being standardized. For a more user-focussed explanation, take a look at the **[Component Model Documentation]**.
+This repository is where the component model is being standardized. For a more user-focused explanation, take a look at the **[Component Model Documentation]**.
 
 This repository describes the high-level [goals], [use cases], [design choices]
 and [FAQ] of the component model as well as a more-detailed [assembly-level explainer], [IDL],

design/high-level/Goals.md

@@ -13,7 +13,7 @@
      language or family of languages.
    * *Embeddability*: design components to be embedded in a diverse set of
      host execution environments, including browsers, servers, intermediaries,
-     small devices and data-intensive systems.
+     small devices, and data-intensive systems.
    * *Optimizability*: maximize the static information available to
      Ahead-of-Time compilers to minimize the cost of instantiation and
      startup.
@@ -31,7 +31,7 @@
 ## Non-goals
 
 1. Don't attempt to solve 100% of WebAssembly embedding scenarios.
-   * Some scenarios will require features in conflict with the above-mentioned goal.
+   * Some scenarios will require features in conflict with the above-mentioned goals.
    * With the layered approach to specification, unsupported embedding
      scenarios can be solved via alternative layered specifications or by
      directly embedding the existing WebAssembly core specification.

design/high-level/UseCases.md

@@ -148,11 +148,11 @@ the programming language):
    full cost and OS-dependency of splitting their program into multiple processes
    by instead having each component do one thing well and using the component
    model to compose their program as a hierarchy of components.
-6. An application developer composes multiple independently-developed
-   components that import and export the same interface (e.g., a HTTP
-   request-handling interface) by linking them together, exports-to-imports, being
-   able to create recursive, branching DAGs of linked components not otherwise
-   expressible with classic Unix-style pipelines.
+6. An application developer composes multiple independently-developed components
+   that import and export the same interface (e.g., an HTTP request-handling
+   interface). By linking these components from exports to imports, the developer
+   can create recursive, branching DAGs of linked components, achieving
+   configurations not possible with classic Unix-style pipelines.
 
 In all the above use cases, the developer has an additional goal of keeping the
 component reuse as a private, fully-encapsulated implementation detail that

design/mvp/Binary.md

@@ -266,7 +266,7 @@ Notes:
 canon    ::= 0x00 0x00 f:<core:funcidx> opts:<opts> ft:<typeidx> => (canon lift f opts type-index-space[ft])
            | 0x01 0x00 f:<funcidx> opts:<opts>                   => (canon lower f opts (core func))
            | 0x02 rt:<typeidx>                                   => (canon resource.new rt (core func))
-           | 0x03 rt:<typdidx>                                   => (canon resource.drop rt (core func))
+           | 0x03 rt:<typeidx>                                   => (canon resource.drop rt (core func))
            | 0x04 rt:<typeidx>                                   => (canon resource.rep rt (core func))
            | 0x05 ft:<typeidx>                                   => (canon thread.spawn ft (core func))
            | 0x06                                                => (canon thread.hw_concurrency (core func))

design/mvp/Explainer.md

@@ -2,7 +2,7 @@
 
 This explainer walks through the assembly-level definition of a
 [component](../high-level) and the proposed embedding of components into native
-JavaScript runtimes. For a more user-focussed explanation, take a look at the
+JavaScript runtimes. For a more user-focused explanation, take a look at the
 **[Component Model Documentation]**.
 
 * [Gated features](#gated-features)