Add short IDs for most long section names

I've left off sections that are headings for their whole document.

1 files changed, 12 insertions, 12 deletions

diff --git a/spec/rend-spec-v3/introduction-protocol.md b/spec/rend-spec-v3/introduction-protocol.md
index f4e6358..ebf51b2 100644
--- a/spec/rend-spec-v3/introduction-protocol.md
+++ b/spec/rend-spec-v3/introduction-protocol.md
@@ -1,6 +1,6 @@
 <a id="rend-spec-v3.txt-3"></a>
 
-# The introduction protocol \[INTRO-PROTOCOL\]
+# The introduction protocol {#INTRO-PROTOCOL}
 
 The introduction protocol proceeds in three steps.
 
@@ -30,11 +30,11 @@ the introduction request to the client.
 
 <a id="rend-spec-v3.txt-3.1"></a>
 
-## Registering an introduction point \[REG_INTRO_POINT\]
+## Registering an introduction point {#REG_INTRO_POINT}
 
 <a id="rend-spec-v3.txt-3.1.1"></a>
 
-### Extensible ESTABLISH_INTRO protocol. \[EST_INTRO\]
+### Extensible ESTABLISH_INTRO protocol. {#EST_INTRO}
 
 When a hidden service is establishing a new introduction point, it
 sends an ESTABLISH_INTRO cell with the following contents:
@@ -115,7 +115,7 @@ later in INTRODUCE1 cells.
 
 <a id="rend-spec-v3.txt-3.1.1.1"></a>
 
-#### Denial-of-Service Defense Extension. \[EST_INTRO_DOS_EXT\]
+#### Denial-of-Service Defense Extension. {#EST_INTRO_DOS_EXT}
 
 This extension can be used to send Denial-of-Service (DoS) parameters to
 the introduction point in order for it to apply them for the introduction
@@ -215,7 +215,7 @@ authentication keys.
 
 <a id="rend-spec-v3.txt-3.1.3"></a>
 
-### Acknowledging establishment of introduction point \[INTRO_ESTABLISHED\]
+### Acknowledging establishment of introduction point {#INTRO_ESTABLISHED}
 
 After setting up an introduction circuit, the introduction point reports its
 status back to the hidden service host with an INTRO_ESTABLISHED cell.
@@ -240,7 +240,7 @@ apply to the extension fields here as described \[EST_INTRO\] above.
 
 <a id="rend-spec-v3.txt-3.2"></a>
 
-## Sending an INTRODUCE1 cell to the introduction point. \[SEND_INTRO1\]
+## Sending an INTRODUCE1 cell to the introduction point. {#SEND_INTRO1}
 
 In order to participate in the introduction protocol, a client must
 know the following:
@@ -267,7 +267,7 @@ or that its request will not succeed.
 
 <a id="rend-spec-v3.txt-3.2.1"></a>
 
-### INTRODUCE1 cell format \[FMT_INTRO1\]
+### INTRODUCE1 cell format {#FMT_INTRO1}
 
 When a client is connecting to an introduction point, INTRODUCE1 cells
 should be of the form:
@@ -310,7 +310,7 @@ apply to the extension fields here as described \[EST_INTRO\] above.
 
 <a id="rend-spec-v3.txt-3.2.2"></a>
 
-### INTRODUCE_ACK cell format. \[INTRO_ACK\]
+### INTRODUCE_ACK cell format. {#INTRO_ACK}
 
 An INTRODUCE_ACK cell has the following fields:
 
@@ -335,7 +335,7 @@ apply to the extension fields here as described \[EST_INTRO\] above.
 
 <a id="rend-spec-v3.txt-3.3"></a>
 
-## Processing an INTRODUCE2 cell at the hidden service. \[PROCESS_INTRO2\]
+## Processing an INTRODUCE2 cell at the hidden service. {#PROCESS_INTRO2}
 
 Upon receiving an INTRODUCE2 cell, the hidden service host checks whether
 the AUTH_KEY or LEGACY_KEY_ID field matches the keys for this
@@ -432,7 +432,7 @@ apply to the extension fields here as described \[EST_INTRO\] above.
 
 <a id="rend-spec-v3.txt-3.3.1"></a>
 
-### Introduction handshake encryption requirements \[INTRO-HANDSHAKE-REQS\]
+### Introduction handshake encryption requirements {#INTRO-HANDSHAKE-REQS}
 
 When decoding the encrypted information in an INTRODUCE2 cell, a
 hidden service host must be able to:
@@ -580,7 +580,7 @@ AES-128 and SHA1 for this hop, we use AES-256 and SHA3-256.
 
 <a id="rend-spec-v3.txt-3.4"></a>
 
-## Authentication during the introduction phase. \[INTRO-AUTH\]
+## Authentication during the introduction phase. {#INTRO-AUTH}
 
 Hidden services may restrict access only to authorized users.
 One mechanism to do so is the credential mechanism, where only users who
@@ -590,7 +590,7 @@ There is one defined authentication type: `ed25519`.
 
 <a id="rend-spec-v3.txt-3.4.1"></a>
 
-### Ed25519-based authentication `ed25519`
+### Ed25519-based authentication `ed25519` {#ed25519-auth}
 
 (NOTE: This section is not implemented by Tor.  It is likely
 that we would want to change its design substantially before