Adopt change 2.S2 proposed by the GLD WG in #254.

spec/latest/json-ld/index.html

@@ -279,18 +279,20 @@ <h1>Design Goals and Rationale</h1>
    <dd>The JSON-LD syntax must be very terse and human readable, requiring as
     little effort as possible from the developer.</dd>
    <dt>Zero Edits, most of the time</dt>
-   <dd>JSON-LD must make the transition to JSON-LD as simple as possible. In many cases,
+   <dd>JSON-LD must ensure a smooth and simple transition from existing 
+     JSON-based systems. In many cases,
      zero edits to the JSON document and the addition of one line to the HTTP response
      should suffice (see <a class="sectionRef" href="#interpreting-json-as-json-ld"></a>).
      This allows organizations that have
      already deployed large JSON-based infrastructure to use JSON-LD's features
      in a way that is not disruptive to their day-to-day operations and is
      transparent to their current customers. However, there are times where
-     mapping JSON to a graph representation is more complex than a simple one-line
-     change. In these instances, rather than extending JSON-LD to support an
-     esoteric use case, we chose not to support the use case. While Zero Edits is
-     a design goal, it is not always possible without adding great complexity
-     to the language. We should focus on simplicity when possible.</dd>
+     mapping JSON to a graph representation is a complex undertaking. 
+     In these instances, rather than extending JSON-LD to support 
+     esoteric use cases, we chose not to support the use case. While Zero 
+     Edits is a design goal, it is not always possible without adding 
+     great complexity to the language. We should focus on simplicity when 
+     possible.</dd>
     <dt>Usable as RDF</dt>
     <dd>JSON-LD must be usable by developers as
       idiomatic JSON, with no need to understand RDF [[RDF11-CONCEPTS]].