doc/tips/Decentralized_repository_behind_a_Firewall.mdwn

@@ -1,4 +1,4 @@
-If you're anything like me, you have a copy of your annex on a computer running at home¹, set up so you can access it from anywhere like this:
+If you're anything like me¹, you have a copy of your annex on a computer running at home², set up so you can access it from anywhere like this:
 
     ssh myhome.no-ip.org
 
@@ -21,7 +21,7 @@ You can now add your *on-the-go* computer as a remote on your *home* computer. U
     cd ~/annex
     git annex remote add on-the-go ssh://localhost:2201/home/myuser/annex
 
-Now you can run normal annex operations, as long as the port forwarding shell is running².
+Now you can run normal annex operations, as long as the port forwarding shell is running³.
 
     git annex sync
     git annex get on-the-go some/big/file
@@ -51,6 +51,8 @@ In any case, the setup is much, much, much more secure than Dropbox. With Dropbo
 * A truly huge amount of eyes connected to incredibly smart brains have looked at openssh and found it secure. Everybody trusts openssh. With dropbox, there is, well, dropbox. Whoever that is.
 -----
 
-¹ My always-on computer at home is a raspberry pi with a 32GB USB stick. Best self-hosted dropbox you could imagine.
+¹ Me=Carlo, not Joey. Just noting so this you can direct potential flames at the correct person.
 
-² You can just forward the port, but not open a shell, by adding the -N command. This could be useful for connecting on startup, e.g. in /etc/rc.local. I prefer to open the shell to forward the ports, maybe use it, and close it to stop it.
+² My always-on computer at home is a raspberry pi with a 32GB USB stick. Best self-hosted dropbox you could imagine.
+
+³ You can just forward the port, but not open a shell, by adding the -N command. This could be useful for connecting on startup, e.g. in /etc/rc.local. I prefer to open the shell to forward the ports, maybe use it, and close it to stop it.