From 735de03e07cc6a2c63e76c38b5359415dc1750e3 Mon Sep 17 00:00:00 2001
From: Travis Ralston <travpc@gmail.com>
Date: Fri, 31 Aug 2018 17:40:32 -0600
Subject: [PATCH] Add r0 version links

These were missed in the release process.
---
 specification/application_service_api.rst | 7 ++++---
 specification/client_server_api.rst       | 1 +
 specification/identity_service_api.rst    | 1 +
 3 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/specification/application_service_api.rst b/specification/application_service_api.rst
index 8af10df8..b2a1f107 100644
--- a/specification/application_service_api.rst
+++ b/specification/application_service_api.rst
@@ -52,6 +52,7 @@ Other versions of this specification
 The following other versions are also available, in reverse chronological order:
 
 - `HEAD <https://matrix.org/docs/spec/application_service/unstable.html>`_: Includes all changes since the latest versioned release.
+- `r0.1.0 <https://matrix.org/docs/spec/application_service/r0.1.0.html>`_
 
 
 Application Services
@@ -174,7 +175,7 @@ An example registration file for an IRC-bridging application service is below:
         - exclusive: true
           regex: "@_irc_bridge_.*"
       aliases:
-        - exclusive: false 
+        - exclusive: false
           regex: "#_irc_bridge_.*"
       rooms: []
 
@@ -318,7 +319,7 @@ Inputs:
 Notes:
  - This applies to all aspects of the Client-Server API, except for Account Management.
  - The ``as_token`` is inserted into ``access_token`` which is usually where the
-   client token is, such as via the query string or ``Authorization`` header. This 
+   client token is, such as via the query string or ``Authorization`` header. This
    is done on purpose to allow application services to reuse client SDKs.
  - The ``access_token`` should be supplied through the ``Authorization`` header where
    possible to prevent the token appearing in HTTP request logs by accident.
@@ -425,7 +426,7 @@ Referencing messages from a third party network
 Application services should include an ``external_url`` in the ``content`` of
 events it emits to indicate where the message came from. This typically applies
 to application services that bridge other networks into Matrix, such as IRC,
-where an HTTP URL may be available to reference. 
+where an HTTP URL may be available to reference.
 
 Clients should provide users with a way to access the ``external_url`` if it
 is present. Clients should additionally ensure the URL has a scheme of ``https``
diff --git a/specification/client_server_api.rst b/specification/client_server_api.rst
index dd7a3e19..e6103623 100644
--- a/specification/client_server_api.rst
+++ b/specification/client_server_api.rst
@@ -45,6 +45,7 @@ Other versions of this specification
 The following other versions are also available, in reverse chronological order:
 
 - `HEAD <https://matrix.org/docs/spec/client_server/unstable.html>`_: Includes all changes since the latest versioned release.
+- `r0.4.0 <https://matrix.org/docs/spec/client_server/r0.4.0.html>`_
 - `r0.3.0 <https://matrix.org/docs/spec/client_server/r0.3.0.html>`_
 - `r0.2.0 <https://matrix.org/docs/spec/client_server/r0.2.0.html>`_
 - `r0.1.0 <https://matrix.org/docs/spec/client_server/r0.1.0.html>`_
diff --git a/specification/identity_service_api.rst b/specification/identity_service_api.rst
index 8d90037e..1bcdeff0 100644
--- a/specification/identity_service_api.rst
+++ b/specification/identity_service_api.rst
@@ -51,6 +51,7 @@ Other versions of this specification
 The following other versions are also available, in reverse chronological order:
 
 - `HEAD <https://matrix.org/docs/spec/identity_service/unstable.html>`_: Includes all changes since the latest versioned release.
+- `r0.1.0 <https://matrix.org/docs/spec/identity_service/r0.1.0.html>`_
 
 General principles
 ------------------