Tidy readme

README.org

@@ -26,6 +26,7 @@ Once it's running it should give you an ocapn sturdyref URI that looks like
 ocapn://lm3diirygy3timbrmvrteytdgvqtmobxge4gcmbwgrrdcntgmzrtknrygfrtqobqmuydkojqmizwmmrwgrtdgzjyme4gkmrvgvtdamtegaydenzhorrxallunrztgmr2yg36awawsxz5gkuoi5t42cc2nxhiz7sxzlfdkfwyk3al3rposhev2.prelay/s/ksmG0sFM-xgypoY7LlJlYNMuDojc-vifcRJxR6AC3P0?host=localhost&port=42069
  #+END_SRC
 This is a "sturdyref" - a reference to an object as text, that can be resolved to a far object in Goblins. Keep this sturdyref around and don't share it, as it gives you the keys to the Prelay.
+
 NOTE: This is not saved across runs, so keep the prelay running as long as you want to do this test, or else you'll have to do this all over again
 
 *** Creating two user accounts
@@ -35,6 +36,7 @@ Now you can go back to a local machine, since you have the sturdyref and can com
    guile prelay-server.scm add-account <admin-sturdyref> username2/chat
  #+END_SRC
 This will give you two more sturdyrefs representing accounts on the Prelay. These should be passed to the users who wish to communicate (send them over some secure method like Signal or Matrix or just copy-pasting!). They shouldn't share these with anyone else.
+
 These are one-time account logins. Think of them like those links you get in emails when signing up for a service. They can only be used once. Consequently this means with goblins-echo you can only send a single messsage per account, but that'll change later when we switch to a REPL-style chat and keep the reference to the send capability in memory.
 *** Creating the listener
 The listener is the one receiving the messages. Now we finally can use our goblin-echo script to create a listener! One of the users can run: