diff options
| author | Neil Johnson <neil@matrix.org> | 2019-02-28 15:20:40 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-02-28 15:20:40 +0000 |
| commit | b649d59332a58182df5936fe7b607dd29c079135 (patch) | |
| tree | 5b2baf32db3f2fd598db4a963d7e996a164955c7 | |
| parent | Update README.rst (diff) | |
| download | synapse-b649d59332a58182df5936fe7b607dd29c079135.tar.xz | |
Update README.rst
| -rw-r--r-- | README.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/README.rst b/README.rst index 1303f59d48..4e2a7fd05a 100644 --- a/README.rst +++ b/README.rst @@ -248,8 +248,8 @@ Note that the server hostname cannot be an alias (CNAME record): it has to point directly to the server hosting the synapse instance. If it is not possible to acquire a certificate valid for you matrix domain, -the correct method is create a Well Known entry. For more details on how to -configure Well Known `see <https://github.com/matrix-org/synapse/blob/master/docs/well_known.md`_ +the correct method is create a .well-known entry. For more details on how to +configure .well-known `see <https://github.com/matrix-org/synapse/blob/master/docs/well_known.md`_ For those of you upgrading your TLS certificate in readiness for Synapse 1.0, please take a look at `our guide <https://github.com/matrix-org/synapse/blob/master/docs/MSC1711_certificates_FAQ.md#configuring-certificates-for-compatibility-with-synapse-100>`_ |