Update standard replies links

ircv3 · Aug 27, 2019 · 16209b1 · 16209b1
1 parent 27b4fed
commit 16209b1
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/extensions/setname.md b/extensions/setname.md
@@ -85,7 +85,7 @@ modified to support it. The proper way to do so is this:
 
 ## Errors
 
-The server MUST use the [standard replies extension][1] to notify the client of
+The server MUST use the [standard replies][] extension to notify the client of
 failed `SETNAME` commands.
 
 If the server rejects the realname as a result of a validation failure, it MUST
@@ -117,4 +117,4 @@ Example with realname rejected by the server
     C: SETNAME :Heute back ich, morgen brau ich, übermorgen hol ich der Königin ihr Kind; ach, wie gut, dass niemand weiß, dass ich Rumpelstilzchen heiß!
     S: FAIL SETNAME INVALID_REALNAME :Realname is not valid
 
-[1]: https://github.com/ircv3/ircv3-specifications/pull/357
+[standard replies]: ../extensions/standard-replies.html
diff --git a/extensions/standard-replies.md b/extensions/standard-replies.md
@@ -40,7 +40,7 @@ Here's what each parameter means:
 
 `<command>` is a case-insensitive, required parameter which is either a command name (e.g. `MODE`, `AUTHENTICATE`, `NICK`, etc), or is `*` to indicate a message that was not spawned from a particular command. This message SHOULD also be given a [label](./labeled-response.html), if one was provided by the client with the original command that spawned this reply.
 
-`<code>` is a case-insensitive, required parameter which lets the client software handle the message appropriately. The [IRCv3 Reply Code Registry](http://ircv3.net/registry.html#reply-codes) lists the reply codes currently in use, and implementers MUST use an existing code if one is already defined.
+`<code>` is a case-insensitive, required parameter which lets the client software handle the message appropriately. The [IRCv3 Reply Code Registry](http://ircv3.net/registry.html) lists the reply codes currently in use, and implementers MUST use an existing code if one is already defined.
 
 Reply codes (especially more widely-applicable ones such as `NO_SUCH_NICK`) may require different action or mean different things when referring to different commands. Because of this, clients acting on an incoming reply code should also take the `<command>` into account, or ensure that the given `<code>` is intended to be globally-unique.