Merge branch 'linklint' into 'main'

Fix linklint script and broken links

See merge request tpo/core/torspec!210

13 files changed, 15 insertions, 15 deletions

diff --git a/bin/check_links b/bin/check_links
index 890ac30..9be7953 100755
--- a/bin/check_links
+++ b/bin/check_links
@@ -24,7 +24,7 @@ xargs -0r -- perl -i~ -pe '
 	s{\bid=("[^"]+")[^<>]*\>}{$&<a name=$1>}g;
 '
 
-linklint -out linklint.errors -error -root $chk_dir /
+linklint -xref -out linklint.errors -error -root $chk_dir /@
 
 cat linklint.errors
 
diff --git a/proposals/340-packed-and-fragmented.md b/proposals/340-packed-and-fragmented.md
index 74af5ca..82adb8e 100644
--- a/proposals/340-packed-and-fragmented.md
+++ b/proposals/340-packed-and-fragmented.md
@@ -31,7 +31,7 @@ This proposal combines ideas from
 [proposal 319](./319-wide-everything.md) (fragmentation) and
 [proposal 325](./325-packed-relay-cells.md) (packed cells).  It requires
 [ntor v3](./332-ntor-v3-with-extra-data.md) and prepares for
-[next-generation relay cryptography](./308-counter-galois-onion).
+[next-generation relay cryptography](./308-counter-galois-onion.md).
 
 Additionally, this proposal has been revised to incorporate another
 protocol change, and move StreamId from the relay cell header into a new,
diff --git a/proposals/BY_INDEX.md b/proposals/BY_INDEX.md
index 5663908..b60a656 100644
--- a/proposals/BY_INDEX.md
+++ b/proposals/BY_INDEX.md
@@ -11,7 +11,7 @@ of these proposals are implemented; some are works in progress; and some
 will never be implemented.
 
 Below are a list of proposals sorted by their proposal number.  See
-[README.md](/proposals/README.md) for a list of proposals sorted by status.
+[BY_STATUS.md](/proposals/BY_STATUS.md) for a list of proposals sorted by status.
 
 * [`000-index.txt`](/proposals/000-index.txt): Index of Tor Proposals [META]
 * [`001-process.txt`](/proposals/001-process.txt): The Tor Proposal Process [META]
diff --git a/proposals/BY_INDEX_template.md b/proposals/BY_INDEX_template.md
index d18dc60..2c8d425 100644
--- a/proposals/BY_INDEX_template.md
+++ b/proposals/BY_INDEX_template.md
@@ -11,6 +11,6 @@ of these proposals are implemented; some are works in progress; and some
 will never be implemented.
 
 Below are a list of proposals sorted by their proposal number.  See
-[README.md](/proposals/README.md) for a list of proposals sorted by status.
+[BY_STATUS.md](/proposals/BY_STATUS.md) for a list of proposals sorted by status.
 
 {BY_INDEX}
diff --git a/spec/bandwidth-file-spec/implementation-details.md b/spec/bandwidth-file-spec/implementation-details.md
index 08fac19..dbc02cc 100644
--- a/spec/bandwidth-file-spec/implementation-details.md
+++ b/spec/bandwidth-file-spec/implementation-details.md
@@ -393,6 +393,6 @@ References:
    The Torflow specification is outdated, and does not match the current
    implementation. See section A.1. for the format produced by Torflow.
 3. [The Tor Directory Protocol](../dir-spec)
-4. [How Tor Version Numbers Work In Tor](../version-spec)
+4. [How Tor Version Numbers Work In Tor](../version-spec.md)
 5. <https://semver.org/>
 ```
diff --git a/spec/path-spec/learning-timeouts.md b/spec/path-spec/learning-timeouts.md
index 89b09a4..e98bac3 100644
--- a/spec/path-spec/learning-timeouts.md
+++ b/spec/path-spec/learning-timeouts.md
@@ -54,7 +54,7 @@ that build time binning is still needed for parameter estimation.
 Once 'cbtmincircs' build times are recorded, Tor clients update the
 distribution parameters and recompute the timeout every circuit completion
 (though
-[see below](#change-in-network)
+[see below](#changes-in-network)
 for when to pause and reset timeout due to
 too many circuits timing out).
 
diff --git a/spec/path-spec/path-selection-constraints.md b/spec/path-spec/path-selection-constraints.md
index 7905466..8cac4fc 100644
--- a/spec/path-spec/path-selection-constraints.md
+++ b/spec/path-spec/path-selection-constraints.md
@@ -26,7 +26,7 @@ constraints:
   (C Tor overrides this with `EnforceDistinctSubnets`;
   Arti overrides this with `ipv[46]_subnet_family_prefix`.)
 - The first node must be a Guard (see
-  discussion [below](./guard-nodes) and in the
+  discussion [below](./guard-nodes.md) and in the
   [guard specification](../guard-spec)).
 - XXXX Choosing the length
 
@@ -64,7 +64,7 @@ position they are being selected for.
 
 These weights are published in the consensus, and are computed as described
 in
-["Computing Bandwidth Weights"](../dir-spec/computing-consensus#computing-bandwidth-weights)
+["Computing Bandwidth Weights"](../dir-spec/computing-consensus.md#computing-bandwidth-weights)
 in the directory specification.
 They are:
 
diff --git a/spec/rend-spec/managing-streams.md b/spec/rend-spec/managing-streams.md
index 56f6f51..a32a352 100644
--- a/spec/rend-spec/managing-streams.md
+++ b/spec/rend-spec/managing-streams.md
@@ -14,7 +14,7 @@ and not set any flags on the begin message.
 > on port 443, a client would send a BEGIN message with
 > the address:port string of `":443"`, and a `FLAGS` value of 0.
 > The 0-values `FLAGS` would not be encoded, according to
-> the instructions for [encoding BEGIN messages](../tor-spec/opening/streams#opening).
+> the instructions for [encoding BEGIN messages](../tor-spec/opening-streams.md#opening).
 
 ## Receiving BEGIN messages { #receive-begin }
 
diff --git a/spec/tor-spec/channels.md b/spec/tor-spec/channels.md
index 5b0020a..046181b 100644
--- a/spec/tor-spec/channels.md
+++ b/spec/tor-spec/channels.md
@@ -33,7 +33,7 @@ whereas clients and bridges SHOULD NOT do so.
 Parties should usually reuse an existing channel
 rather than opening new a channel to the same relay.
 There are exceptions here;
-we discuss them more [below](#XXXX).
+we discuss them more below. <!-- TODO: add anchor link -->
 
 To open a channel,
 a client or relay must know the IP address and port
diff --git a/spec/tor-spec/create-created-cells.md b/spec/tor-spec/create-created-cells.md
index 1e6281c..965cad1 100644
--- a/spec/tor-spec/create-created-cells.md
+++ b/spec/tor-spec/create-created-cells.md
@@ -191,7 +191,7 @@ of each type.
 
 After checking relay identities, extending ORs generate a
 CREATE/CREATE2 cell from the contents of the EXTEND/EXTEND2 cell.
-See [Creating circuits](./#creating-circuits.md#creating-circuits)
+See [Creating circuits](./creating-circuits.md#creating-circuits)
 for details.
 
 The payload of an EXTENDED cell is the same as the payload of a
diff --git a/spec/tor-spec/flow-control.md b/spec/tor-spec/flow-control.md
index bf1abe2..91c04e3 100644
--- a/spec/tor-spec/flow-control.md
+++ b/spec/tor-spec/flow-control.md
@@ -33,7 +33,7 @@ information. See proposal 111 for details.
 Link padding can be created by sending PADDING or VPADDING cells
 along the connection; relay cells of type "DROP" can be used for
 long-range padding.  The payloads of PADDING, VPADDING, or DROP
-cells are filled with padding bytes. See [Cell Packet format](./cell-packet-format#cell-packet-format).
+cells are filled with padding bytes. See [Cell Packet format](./cell-packet-format.md#cell-packet-format).
 
 If the link protocol is version 5 or higher, link level padding is
 enabled as per padding-spec.txt. On these connections, clients may
diff --git a/spec/tor-spec/negotiating-channels.md b/spec/tor-spec/negotiating-channels.md
index 2501d7f..c328e12 100644
--- a/spec/tor-spec/negotiating-channels.md
+++ b/spec/tor-spec/negotiating-channels.md
@@ -10,7 +10,7 @@ which we describe in [another section](./obsolete-channels.md).
 In brief:
  - The initiator starts the handshake
    by [opening a TLS connection](#tls).
- - Both parties send a [VERSIONS](#VERSIONS-cell)
+ - Both parties send a [VERSIONS](#VERSIONS-cells)
    to negotiate the protocol version to use.
  - The responder sends a
    [CERTS cell](#CERTS-cells) to give the
@@ -145,7 +145,7 @@ Relevant certType values are:
 | 7        | Ed25519 identity, signed with RSA identity.
 
 The certificate format for certificate types 1-3 is DER encoded X509.
-For others, the format is as documented in [a later section](./cert-spec.md)
+For others, the format is as documented in [a later section](../cert-spec.md)
 
 Note that type 7 uses a different format from types 4-6.
 
diff --git a/spec/tor-spec/subprotocol-versioning.md b/spec/tor-spec/subprotocol-versioning.md
index 97c4409..780a337 100644
--- a/spec/tor-spec/subprotocol-versioning.md
+++ b/spec/tor-spec/subprotocol-versioning.md
@@ -295,7 +295,7 @@ Describes the communications mechanisms used to bundle circuits together,
 in order to split traffic across multiple paths.
 
 > TODO: This is not yet described here. For details see
-> [Proposal 329](../proposals/329).
+> [Proposal 329](../proposals/329-traffic-splitting.txt).
 
 <a id="tor-spec.txt-9.13"></a>