Fix broken links after zed#5376 (#5377)

README.md

@@ -51,7 +51,7 @@ FROM 'https://data.gharchive.org/2015-01-01-15.json.gz'
 Super-structured data is strongly typed and "polymorphic": any value can take on any type
 and sequences of data need not all conform to a predefined schema.  To this end,
 SuperDB extends the JSON format to support super-structured data in a format called
-[Super JSON](https://zed.brimdata.io/docs/formats/next/jsup) where all JSON values
+[Super JSON](https://zed.brimdata.io/docs/next/formats/jsup) where all JSON values
 are also Super JSON values.  Similarly,
 the [Super Binary](https://zed.brimdata.io/docs/formats/zng) format is an efficient
 binary representation of Super JSON (a bit like Avro) and the

docs/formats/jsup.md

@@ -18,7 +18,7 @@ type for every value expressed in source text.
 Super JSON is also a superset of JSON in that all JSON documents are valid
 Super JSON values.
 
-## 2. The Suepr JSON Format
+## 2. The Super JSON Format
 
 A Super JSON text is a sequence of UTF-8 characters organized either as a bounded input
 or an unbounded stream.

docs/formats/zjson.md

@@ -61,7 +61,7 @@ Also, it is at the whim of a JSON implementation whether
 or not the order of object keys is preserved.
 
 While JSON is well suited for data exchange of generic information, it is not
-sufficient for the [super-structured data model](./README.md#2-zed-a-super-structured-pattern).
+sufficient for the [super-structured data model](./README.md#2-a-super-structured-pattern).
 That said, JSON can be used as an encoding format for super data with another layer
 of encoding on top of a JSON-based protocol.  This allows clients like web apps or
 Electron apps to receive and understand Super JSON and, with the help of client