Hi,
thanks for making this, I might use it at some point.
I only skimmed the first 1/3 of it and have some suggestions:
1.) when showing stuff the user has to enter in some shell (there might be different shells involved at some point, like bash and python shell), replicate the prompt, something like this:
#> pip install django
#> django-admin.py startproject instawallet
#> cd instawallet
that way, the user (always assume he knows nothing) always knows that this is commands he is supposed to enter and in which shell they go. Another upside to this is that you can also replicate the shells answer in cases where this might be reassuring, like so:
#> bitcoind stop
bitcoind stopping
2.) When telling the reader to edit/create some file, you should always state the name of the file clearly. You could also emphasize the filename in the pretext.
Here is an example that leaves me uncertain about what the file should be named and where it goes:
We set up the sqlite database as a file “dev.db”. After that we add “django_bitcoin” and “wallets” to INSTALLED_APPS so that django can find our apps. Also we specify a templates directory. Create a folder “templates” inside the project root.
You're telling the reader to create a folder and then give him some text he should put in a file... which file? db.env? Where does it go? In the templates folder? This is not clear, always be clear on this. This problem is seen in many tutorials: the author makes some assumptions about the users just _knowing_ where some config directives or newly created files should go. It might be crystal-clear to the author (who is an expert), but keep in mind that all the stuff you write is probably new to the reader, so he is very uncertain about things and it helps to reassure him by stating the obvious.
Other than that your tutorial seems great!
I will give you more feedback once I actually go through with it.
Thanks!