Reverted "[1.7.x] Made minor edits to docs/intro/tutorial01.text"

This reverts commit ba4237c.

Claude asked that these fixes not be backported as they affect translations.

docs/intro/tutorial01.txt

@@ -128,7 +128,7 @@ These files are:
 Database setup
 --------------
 
-Now, open up :file:`mysite/settings.py`. It's a normal Python module with
+Now, edit :file:`mysite/settings.py`. It's a normal Python module with
 module-level variables representing Django settings.
 
 By default, the configuration uses SQLite. If you're new to databases, or
@@ -270,7 +270,7 @@ It worked!
 
     If you want to change the server's IP, pass it along with the port. So to
     listen on all public IPs (useful if you want to show off your work on other
-    computers on your network), use:
+    computers), use:
 
     .. code-block:: console
 
@@ -525,8 +525,8 @@ Note the following:
 * It's tailored to the database you're using, so database-specific field types
   such as ``auto_increment`` (MySQL), ``serial`` (PostgreSQL), or ``integer
   primary key autoincrement`` (SQLite) are handled for you automatically. Same
-  goes for the quoting of field names -- e.g., using double quotes or 
-  single quotes.
+  goes for quoting of field names -- e.g., using double quotes or single
+  quotes.
 
 * The :djadmin:`sqlmigrate` command doesn't actually run the migration on your
   database - it just prints it to the screen so that you can see what SQL
@@ -566,10 +566,10 @@ but for now, remember the three-step guide to making model changes:
 * Run :djadmin:`python manage.py migrate <migrate>` to apply those changes to
   the database.
 
-The reason that there are separate commands to make and apply migrations is 
-because you'll commit migrations to your version control system and ship them 
-with your app; they not only make your development easier, they're also 
-useable by other developers and in production.
+The reason there's separate commands to make and apply migrations is because
+you'll commit migrations to your version control system and ship them with
+your app; they not only make your development easier, they're also useable by
+other developers and in production.
 
 Read the :doc:`django-admin.py documentation </ref/django-admin>` for full
 information on what the ``manage.py`` utility can do.