typos

Author: Fil

examples/websites/README.md

@@ -26,7 +26,7 @@ in your web browser! Next, to view it coming from another ipfs node, you can try
 rather ugly. Lets look at some ways to get rid of them.
 
 First, you can do a simple DNS TXT record, containing `dnslink=/ipfs/$SITE_HASH`.
-Once that record propogates, you should be able to view your site at
+Once that record propagates, you should be able to view your site at
 `http://localhost:8080/ipns/your.domain`. Now thats quite a bit cleaner.
 You can also try this on the gateway at `http://gateway.ipfs.io/ipns/your.domain`
 
@@ -46,12 +46,12 @@ Published to <your peer id>: /ipfs/$SITE_HASH
 Now, you can test that it worked by viewing: `http://localhost:8080/ipns/<your peer id>`.
 And also try the same link on the public gateway. Once you're convinced that works,
 lets again hide the hash. Change your DNS TXT record to `dnslink=/ipns/<your peer id>`,
-wait for that record to propogate, and then try accessing `http://localhost:8080/ipns/your.domain`.
+wait for that record to propagate, and then try accessing `http://localhost:8080/ipns/your.domain`.
 
 At this point, you have a website on ipfs/ipns, and you may be wondering how
 you could expose it at `http://your.domain`, so that the Internet users of
 today may access it too without them having to know about any of this. It's
-actually surpisingly simple to do, all you need for this is your previously
+actually surprisingly simple to do, all you need for this is your previously
 created TXT record and to point the A record of `your.domain` to the IP
 address of an ipfs daemon that listens on port 80 for HTTP requests (such as
 `gateway.ipfs.io`). The users' browsers will send `your.domain` in the Host
@@ -60,12 +60,12 @@ gateway will recognize `your.domain` as an IPNS name, and so it will serve
 from under `/ipns/your.domain/` instead of `/`.
 
 So, if you point `your.domain`'s A record to the IP of `gateway.ipfs.io`, and
-then wait for the DNS to propogate, then anyone should be able to access your
+then wait for the DNS to propagate, then anyone should be able to access your
 ipfs-hosted site without any extra configuration simply at
 `http://your.domain`.
 
 Alternatively, it is possible to use CNAME records to point at the DNS records
-of the gateway. This way, IP addresses of the gateway are automtically
+of the gateway. This way, IP addresses of the gateway are automatically
 updated. Note however that CNAME records to not allow for other records, such
 as a TXT to refer to the ipfs/ipns record. Because of this, ipfs allows to
 create a DNS TXT record for `_dnslink.your.domain` with