diff options
| -rw-r--r-- | users/Profpatsch/netencode/README.md (renamed from users/Profpatsch/netencode/spec.md) | 0 | ||||
| -rw-r--r-- | users/Profpatsch/netstring/README.md | 2 |
2 files changed, 1 insertions, 1 deletions
diff --git a/users/Profpatsch/netencode/spec.md b/users/Profpatsch/netencode/README.md index 3058e36eaf5c..3058e36eaf5c 100644 --- a/users/Profpatsch/netencode/spec.md +++ b/users/Profpatsch/netencode/README.md diff --git a/users/Profpatsch/netstring/README.md b/users/Profpatsch/netstring/README.md index 4413d88ee430..b8daea11d158 100644 --- a/users/Profpatsch/netstring/README.md +++ b/users/Profpatsch/netstring/README.md @@ -10,7 +10,7 @@ foo! -> 4:foo!, They can be used to encode e.g. lists by simply concatenating and reading them in one-by-one. -If you need a more complex encoding, you could start encoding e.g. tuples as netstrings-in-netstrings, or you could use [`netencode`](../netcencode/spec.md) instead, which is what-if-json-but-netstrings, and takes the idea of netstrings to their logical conclusion. +If you need a more complex encoding, you could start encoding e.g. tuples as netstrings-in-netstrings, or you could use [`netencode`](../netencode/README.md) instead, which is what-if-json-but-netstrings, and takes the idea of netstrings to their logical conclusion. Resources: |