deploy: 9b7f755

Author: Logofile

editions/features/index.html

@@ -138,7 +138,7 @@
 </span></span><span style=display:flex><span>    <span style=color:#000>Name</span><span style=color:#000;font-weight:700>:</span>  <span style=color:#4e9a06>&#34;John Doe&#34;</span><span style=color:#000;font-weight:700>,</span>
 </span></span><span style=display:flex><span>    <span style=color:#000>Email</span><span style=color:#000;font-weight:700>:</span> <span style=color:#4e9a06>&#34;[email protected]&#34;</span><span style=color:#000;font-weight:700>,</span>
 </span></span><span style=display:flex><span>    <span style=color:#000>Phones</span><span style=color:#000;font-weight:700>:</span> <span style=color:#000;font-weight:700>[]</span><span style=color:#ce5c00;font-weight:700>*</span><span style=color:#000>pb</span><span style=color:#000;font-weight:700>.</span><span style=color:#000>Person_PhoneNumber</span><span style=color:#000;font-weight:700>{</span>
-</span></span><span style=display:flex><span>        <span style=color:#000;font-weight:700>{</span><span style=color:#000>Number</span><span style=color:#000;font-weight:700>:</span> <span style=color:#4e9a06>&#34;555-4321&#34;</span><span style=color:#000;font-weight:700>,</span> <span style=color:#000>Type</span><span style=color:#000;font-weight:700>:</span> <span style=color:#000>pb</span><span style=color:#000;font-weight:700>.</span><span style=color:#000>Person_PHONE_TYPE_HOME</span><span style=color:#000;font-weight:700>},</span>
+</span></span><span style=display:flex><span>        <span style=color:#000;font-weight:700>{</span><span style=color:#000>Number</span><span style=color:#000;font-weight:700>:</span> <span style=color:#4e9a06>&#34;555-4321&#34;</span><span style=color:#000;font-weight:700>,</span> <span style=color:#000>Type</span><span style=color:#000;font-weight:700>:</span> <span style=color:#000>pb</span><span style=color:#000;font-weight:700>.</span><span style=color:#000>PhoneType_PHONE_TYPE_HOME</span><span style=color:#000;font-weight:700>},</span>
 </span></span><span style=display:flex><span>    <span style=color:#000;font-weight:700>},</span>
 </span></span><span style=display:flex><span><span style=color:#000;font-weight:700>}</span>
 </span></span></code></pre></div><h2 id=writing-a-message>Writing a Message</h2><p>The whole purpose of using protocol buffers is to serialize your data so that it

editions/overview/index.html

@@ -27,7 +27,7 @@
 Accessor will report the field as being <em>set</em> and will return something that
 represents <code>2</code>.</li><li><strong>Closed</strong> enums will parse the value <code>2</code> and store it in the message&rsquo;s
 unknown field set. Accessors will report the field as being <em>unset</em> and will
-return the enum&rsquo;s default value.</li></ul><h2 id=implications-of-closed-enums>Implications of <em>Closed</em> Enums</h2><p>The behavior of <em>closed</em> enums has unexpected consquences when parsing a
+return the enum&rsquo;s default value.</li></ul><h2 id=implications-of-closed-enums>Implications of <em>Closed</em> Enums</h2><p>The behavior of <em>closed</em> enums has unexpected consequences when parsing a
 repeated field. When a <code>repeated Enum</code> field is parsed all unknown values will
 be placed in the
 <a href=/programming-guides/proto3/#unknowns>unknown field</a>

getting-started/gotutorial/index.html

@@ -71,7 +71,7 @@
 </span></span></span></code></pre></div><p>Depending on the target language, the generated API would generally include
 several methods:</p><ul><li>A hazzer for the oneof: <code>has_foo</code></li><li>A <em>oneof case</em> method: <code>foo</code></li><li>Hazzers for the members: <code>has_a</code>, <code>has_b</code></li><li>Getters for the members: <code>a</code>, <code>b</code></li></ul><p>Repeated fields and maps do not track presence: there is no distinction between
 an <em>empty</em> and a <em>not-present</em> repeated field.</p><h3 id=presence-in-proto3-apis>Presence in Proto3 APIs</h3><p>This table outlines whether presence is tracked for fields in proto3 APIs (both
-for generated APIs and using dynamic reflection):</p><table><thead><tr><th>Field type</th><th><code>optional</code></th><th>Explicit Presence</th></tr></thead><tbody><tr><td>Singular numeric (integer or floating point)</td><td>No</td><td></td></tr><tr><td>Singular enum</td><td>No</td><td></td></tr><tr><td>Singular string or bytes</td><td>No</td><td></td></tr><tr><td>Singular numeric (integer or floating point)</td><td>Yes</td><td>✔️</td></tr><tr><td>Singular enum</td><td>Yes</td><td>✔️</td></tr><tr><td>Singular string or bytes</td><td>Yes</td><td>✔️</td></tr><tr><td>Singular message</td><td>Yes</td><td>✔️</td></tr><tr><td>Singular message</td><td>No</td><td>✔️</td></tr><tr><td>Repeated</td><td>N/A</td><td></td></tr><tr><td>Oneofs</td><td>N/A</td><td>✔️</td></tr><tr><td>Maps</td><td>N/A</td><td></td></tr></tbody></table><p>Similar to proto2 APIs, proto3 does not track presence explicitly for repeated
+for generated APIs and using dynamic reflection):</p><table><thead><tr><th>Field type</th><th><code>optional</code></th><th>Explicit Presence</th></tr></thead><tbody><tr><td>Singular numeric (integer or floating point)</td><td>No</td><td></td></tr><tr><td>Singular numeric (integer or floating point)</td><td>Yes</td><td>✔️</td></tr><tr><td>Singular enum</td><td>No</td><td></td></tr><tr><td>Singular enum</td><td>Yes</td><td>✔️</td></tr><tr><td>Singular string or bytes</td><td>No</td><td></td></tr><tr><td>Singular string or bytes</td><td>Yes</td><td>✔️</td></tr><tr><td>Singular message</td><td>No</td><td>✔️</td></tr><tr><td>Singular message</td><td>Yes</td><td>✔️</td></tr><tr><td>Repeated</td><td>N/A</td><td></td></tr><tr><td>Oneofs</td><td>N/A</td><td>✔️</td></tr><tr><td>Maps</td><td>N/A</td><td></td></tr></tbody></table><p>Similar to proto2 APIs, proto3 does not track presence explicitly for repeated
 fields. Without the <code>optional</code> label, proto3 APIs do not track presence for
 basic types (numeric, string, bytes, and enums), either. Oneof fields
 affirmatively expose presence, although the same set of hazzer methods may not

index.html

@@ -944,8 +944,8 @@
 serializing, parsing, and performing other common operations on your
 message types. This code is highly optimized.</li><li><code>CODE_SIZE</code>: The protocol buffer compiler will generate minimal classes
 and will rely on shared, reflection-based code to implement
-serialialization, parsing, and various other operations. The generated
-code will thus be much smaller than with <code>SPEED</code>, but operations will be
+serialization, parsing, and various other operations. The generated code
+will thus be much smaller than with <code>SPEED</code>, but operations will be
 slower. Classes will still implement exactly the same public API as they
 do in <code>SPEED</code> mode. This mode is most useful in apps that contain a very
 large number of <code>.proto</code> files and do not need all of them to be

overview/index.html

@@ -646,8 +646,8 @@
 serializing, parsing, and performing other common operations on your
 message types. This code is highly optimized.</li><li><code>CODE_SIZE</code>: The protocol buffer compiler will generate minimal classes
 and will rely on shared, reflection-based code to implement
-serialialization, parsing, and various other operations. The generated
-code will thus be much smaller than with <code>SPEED</code>, but operations will be
+serialization, parsing, and various other operations. The generated code
+will thus be much smaller than with <code>SPEED</code>, but operations will be
 slower. Classes will still implement exactly the same public API as they
 do in <code>SPEED</code> mode. This mode is most useful in apps that contain a very
 large number of <code>.proto</code> files and do not need all of them to be