README.md

@@ -1,4 +1,4 @@
-# Bitcoin Cash Metadata Registry cashing server.
+# Bitcoin Cash Metadata Registry caching server
 
 Adding metadata to boring payments is a very powerful idea to increase the
 value of the basic financial system we are building in Bitcoin Cash.
@@ -16,7 +16,7 @@ images is metadata that is useful. Your wallet can avoid showing you
 "collectibles" that are nothing more than advertisements or scams if that
 metadata is available.
 
-# A cashing metadata server
+## A caching metadata server
 
 For the wallet or website there is a real challenge getting hold of the
 metadata because it is by its nature decentralized and people can create
@@ -36,7 +36,7 @@ The solution is to have a central webserver to collect and distribute those
 materials which makes it easier for wallets and websites to find the data
 they need.
 
-# Permissioned
+## Permissioned
 
 The idea of anyone being able to create a token or identity is very
 powerful and allows for great innovation and freedom.
@@ -62,7 +62,7 @@ What this project introduces is several trust levels
 informed choices to the user. When the trust is specifically stated to be
 bad, the wallet will be able to just ignore the spam they received.
 
-# How would a wallet or website use this?
+## How would a wallet or website use this?
 
 My own webserver is running on bcmr.flowee.cash and there you can find the
 various metadata.
@@ -86,10 +86,8 @@ For example when a user pays in a store, they may receive an auth-chain ID.
 Which is just like a transaction-id, a 64 character hexadecimal.
 
 There is a single json you can download with the ID.json as a name. With
-details like the name, a description and image urls. As this is a cashing
+details like the name, a description and image urls. As this is a caching
 server you can find the images on the server too.
 
 This json includes a trust field, as set by the server operator. Imposers
 or spam will not stand a chance if the wallet uses that.
-
-