Script updating gh-pages from 75d3646. [ci skip]

IETF-OPSAWG-WG · Apr 25, 2024 · f6d754d · f6d754d
1 parent a3b5110
commit f6d754d
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 14 deletions.
diff --git a/draft-ietf-opsawg-pcapng.html b/draft-ietf-opsawg-pcapng.html
@@ -1965,7 +1965,7 @@ <h4 id="name-custom-options">
 Header Block it is within the scope of.<a href="#section-3.5.1-4.3.1" class="pilcrow">¶</a></p>
 </li>
             <li class="normal" id="section-3.5.1-4.4">
-              <p id="section-3.5.1-4.4.1">Custom Data: the custom data, padded to a 32 bit boundary.<a href="#section-3.5.1-4.4.1" class="pilcrow">¶</a></p>
+              <p id="section-3.5.1-4.4.1">Custom Data: the custom data, padded to a 32-bit boundary.<a href="#section-3.5.1-4.4.1" class="pilcrow">¶</a></p>
 </li>
           </ul>
 </section>
@@ -3093,7 +3093,7 @@ <h4 id="name-enhanced-packet-block-flags">
               </tr>
               <tr>
                 <td class="text-left" rowspan="1" colspan="1">16-31</td>
-                <td class="text-left" rowspan="1" colspan="1">link-layer-dependent errors (Bit 31 = symbol error, Bit 30 = preamble error, Bit 29 = Start Frame Delimiter error, Bit 28 = unaligned frame error, Bit 27 = wrong Inter Frame Gap error, Bit 26 = packet too short error, Bit 25 = packet too long error, Bit 24 = CRC error, other?? are 16 bit enough?).</td>
+                <td class="text-left" rowspan="1" colspan="1">link-layer-dependent errors (Bit 31 = symbol error, Bit 30 = preamble error, Bit 29 = Start Frame Delimiter error, Bit 28 = unaligned frame error, Bit 27 = wrong Inter Frame Gap error, Bit 26 = packet too short error, Bit 25 = packet too long error, Bit 24 = CRC error, other?? are 16 bits enough?).</td>
               </tr>
             </tbody>
           </table>
@@ -3761,7 +3761,7 @@ <h3 id="name-decryption-secrets-block">
 octets.<a href="#section-4.7-6.4.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="section-4.7-6.5">
-            <p id="section-4.7-6.5.1">Secrets Data: binary data containing secrets, padded to a 32 bit
+            <p id="section-4.7-6.5.1">Secrets Data: binary data containing secrets, padded to a 32-bit
 boundary.<a href="#section-4.7-6.5.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="section-4.7-6.6">
@@ -3878,7 +3878,7 @@ <h3 id="name-decryption-secrets-block">
 the <a href="https://zigbeealliance.org/">ZigBee Specification</a> 05-3473-21 (R21) section 4.2.2.
 The NWK Key is a 16 octet binary AES-128 key used to secure NWK Level frames
 within a single PAN. The NWK key is immediately followed by the
-2 octet (16 bit) network PANID in little endian format. If and when
+2-octet (16-bit) network PANID in little endian format. If and when
 the NWK Key changes a new DSB will contain the new NWK Key.<a href="#section-4.7-11.2.1" class="pilcrow">¶</a></p>
 </dd>
         <dd class="break"></dd>
@@ -3889,8 +3889,8 @@ <h3 id="name-decryption-secrets-block">
             <p id="section-4.7-12.2.1">ZigBee APS Key.
 Application Support Link Key as described in the <a href="https://zigbeealliance.org/">ZigBee Specification</a> 05-3473-21 (R21) section 4.4. Each 16 octet binary AES-128 key secures
 frames exchanged between a pair of network nodes. The APS Key is
-immediately followed by the 2 octet (16 bit) network PANID in
-little endian format. The PANID is followed by the 2 octet (16 bit)
+immediately followed by the 2-octet (16-bit) network PANID in
+little endian format. The PANID is followed by the 2-octet (16-bit)
 short addresses, in little endian format, of the nodes to which
 the APS Key applies. The numerically lower short address shall come
 first. There is an APS Key DSB for each node pair for which the
@@ -4037,7 +4037,7 @@ <h3 id="name-custom-block">
 Block it is within the scope of.<a href="#section-4.8-5.3.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="section-4.8-5.4">
-            <p id="section-4.8-5.4.1">Custom Data: the custom data, padded to a 32 bit boundary.<a href="#section-4.8-5.4.1" class="pilcrow">¶</a></p>
+            <p id="section-4.8-5.4.1">Custom Data: the custom data, padded to a 32-bit boundary.<a href="#section-4.8-5.4.1" class="pilcrow">¶</a></p>
 </li>
           <li class="normal" id="section-4.8-5.5">
             <p id="section-4.8-5.5.1">Options: optionally, a list of options (formatted according to

diff --git a/draft-ietf-opsawg-pcapng.txt b/draft-ietf-opsawg-pcapng.txt
@@ -592,7 +592,7 @@ Table of Contents
       using the same endianness as the Section Header Block it is within
       the scope of.
 
-   *  Custom Data: the custom data, padded to a 32 bit boundary.
+   *  Custom Data: the custom data, padded to a 32-bit boundary.
 
 3.6.  Data format
 
@@ -1426,7 +1426,7 @@ Table of Contents
     |        | Delimiter error, Bit 28 = unaligned frame error, Bit  |
     |        | 27 = wrong Inter Frame Gap error, Bit 26 = packet too |
     |        | short error, Bit 25 = packet too long error, Bit 24 = |
-    |        | CRC error, other?? are 16 bit enough?).               |
+    |        | CRC error, other?? are 16 bits enough?).              |
     +--------+-------------------------------------------------------+
 
                                  Table 5
@@ -1908,7 +1908,7 @@ Table of Contents
    *  Secrets Length (32 bits): an unsigned integer that indicates the
       size of the following Secrets field, without any padding octets.
 
-   *  Secrets Data: binary data containing secrets, padded to a 32 bit
+   *  Secrets Data: binary data containing secrets, padded to a 32-bit
       boundary.
 
    *  Options: optionally, a list of options (formatted according to the
@@ -2006,7 +2006,7 @@ Table of Contents
            (https://zigbeealliance.org/) 05-3473-21 (R21) section 4.2.2.
            The NWK Key is a 16 octet binary AES-128 key used to secure
            NWK Level frames within a single PAN.  The NWK key is
-           immediately followed by the 2 octet (16 bit) network PANID in
+           immediately followed by the 2-octet (16-bit) network PANID in
            little endian format.  If and when the NWK Key changes a new
            DSB will contain the new NWK Key.
 
@@ -2015,9 +2015,9 @@ Table of Contents
            the ZigBee Specification (https://zigbeealliance.org/)
            05-3473-21 (R21) section 4.4.  Each 16 octet binary AES-128
            key secures frames exchanged between a pair of network nodes.
-           The APS Key is immediately followed by the 2 octet (16 bit)
+           The APS Key is immediately followed by the 2-octet (16-bit)
            network PANID in little endian format.  The PANID is followed
-           by the 2 octet (16 bit) short addresses, in little endian
+           by the 2-octet (16-bit) short addresses, in little endian
            format, of the nodes to which the APS Key applies.  The
            numerically lower short address shall come first.  There is
            an APS Key DSB for each node pair for which the Link Key is
@@ -2134,7 +2134,7 @@ Table of Contents
       encoded using the same endianness as the Section Header Block it
       is within the scope of.
 
-   *  Custom Data: the custom data, padded to a 32 bit boundary.
+   *  Custom Data: the custom data, padded to a 32-bit boundary.
 
    *  Options: optionally, a list of options (formatted according to the
       rules defined in Section 3.5) can be present.  Note that custom