diff --git a/gatsby/content/blog/2020/04/2020-04-06-selfhosting-matrix.mdx b/gatsby/content/blog/2020/04/2020-04-06-selfhosting-matrix.mdx
index 3e87aa185..95d35b999 100644
--- a/gatsby/content/blog/2020/04/2020-04-06-selfhosting-matrix.mdx
+++ b/gatsby/content/blog/2020/04/2020-04-06-selfhosting-matrix.mdx
@@ -88,7 +88,7 @@ sudo apt install matrix-synapse-py3
 ```
 mkdir -p /var/www/dangerousdemos.net/.well-known/matrix
 cd /var/www/dangerousdemos.net/.well-known/matrix
-cat '{ "m.server": "matrix.dangerousdemos.net:443" }' > server
+echo '{ "m.server": "matrix.dangerousdemos.net:443" }' > server
 ```
 
  * **Alternatively**, you could advertise the server via DNS, if you don't have write access to `/.well-known` on your main domain.  However, to prove you are allowed to host the Matrix traffic for dangerousdemos.net, you would have to configure nginx to use the dangerousdemos.net TLS certificate for the matrix.dangerousdemos.net vhost (i.e. the "wrong" one), and in general we think that `/.well-known` is much easier to reason about.  In this case you would advertise the server with an SRV record like this: