Small documentation tweaks, fixes #9000 - thanks, ramiro

git-svn-id: http://code.djangoproject.com/svn/django/trunk@9010 bcc190cf-cafb-0310-a4f2-bffc1f526a37

docs/internals/contributing.txt

@@ -403,7 +403,7 @@ translated, here's what to do:
     * Create translations using the methods described in the :ref:`i18n
       documentation <topics-i18n>`. For this you will use the ``django-admin.py
       makemessages`` tool. In this particular case it should be run from the
-      top-level``django`` directory of the Django source tree.
+      top-level ``django`` directory of the Django source tree.
 
       The script runs over the entire Django source tree and pulls out all
       strings marked for translation. It creates (or updates) a message file in
@@ -415,7 +415,7 @@ translated, here's what to do:
     
     * Repeat the last two steps for the ``djangojs`` domain (by appending the
       ``-d djangojs`` command line option to the ``django-admin.py``
-      invocations.
+      invocations.)
     
     * Create a diff of the ``.po`` file(s) against the current Subversion trunk.
     

docs/intro/tutorial01.txt

@@ -162,6 +162,9 @@ database's connection parameters:
       that file. If the file doesn't exist, it will automatically be created
       when you synchronize the database for the first time (see below).
       
+      When specifying the path, always use forward slashes, even on Windows 
+      (e.g. ``C:/homes/user/mysite/sqlite3.db``).
+      
     * :setting:`DATABASE_USER` -- Your database username (not used for SQLite).
     
     * :setting:`DATABASE_PASSWORD` -- Your database password (not used for