Skip to content

Commit 66423be

Browse files
committed
Minor editorial changes
1 parent fc94573 commit 66423be

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ If any of these values are optional, you'd still have to provide a zero length n
7575
to maintain positional order; however this creates the ambiguity as to whether the intent
7676
is to convey a zero length string or a NULL.
7777

78-
With "keyed" netstrings the values can be presented in any order and optional or NULL
78+
With "keyed" netstrings the values can be presented in any order and optional (or NULL)
7979
values are simply omitted.
8080
In the above example if we assign the "key" of 'n' to Name, 'a' to Age, 'c' to Country and
8181
'h' to Height the series of "keyed" netstrings looks like:
@@ -92,8 +92,8 @@ All perfectly acceptable with "keyed" netstrings.
9292
To gain the most benefit from "keyed" netstrings, the usual strategy is to reserve a
9393
specific key value as an "end-of-message" sentinal which naturally is the last netstring
9494
in the message.
95-
The convention is to use 'z' as the "end-of-message" sentinal as demonstrated in the
96-
examples.
95+
The convention is to use 'z' as the "end-of-message" sentinal as demonstrated in
96+
subsequent examples.
9797

9898
## Installation
9999

0 commit comments

Comments
 (0)