Add "note" box callouts to SAIO for user changes.

The SAIO is purpously cut into two parts, so that you don't have to switch
back and forth between root and your unprivledged user.  Add some "note" box
callouts to highlight this changeover.

Change-Id: I8b1a8f0539eac60d4121bdd4dab01df75ecca207

doc/source/development_saio.rst

@@ -26,7 +26,10 @@ user. Swift processes also run under a separate user and group, set by
 configuration option, and refered as <your-user-name>:<your-group-name>.
 The default user is `swift`, which may not exist on your system.
 
-Perform the following commands as root.
+.. note::
+
+    The instructions in the first first half of this guide are expected to be
+    performed as the root user.
 
 -----------------------
 Installing dependencies
@@ -294,12 +297,17 @@ Optional: Setting up rsyslog for individual logging
   #. `chmod -R g+w /var/log/swift`
   #. `systemctl restart rsyslog.service`
 
+
+.. note::
+
+    Starting here, from this point on, all instructions are expected to be
+    performed as the unprivledged user you selected as <your-user-name>.
+
+
 ----------------
 Getting the code
 ----------------
 
-You can do the following commands as administrator user.
-
   #. Check out the python-swiftclient repo
        `git clone https://github.com/openstack/python-swiftclient.git`
   #. Build a development installation of python-swiftclient
@@ -314,15 +322,12 @@ You can do the following commands as administrator user.
 Fedora 19 or later users might have to perform the following if development
 installation of swift fails::
 
-        pip install -U xattr dnspython
+        sudo pip install -U xattr dnspython
 
 ---------------------
 Configuring each node
 ---------------------
 
-Do the following commands as root, but verify that Swift has access
-to resulting configuration files.
-
 Sample configuration files are provided with all defaults in line-by-line comments.
 
   #. Create `/etc/swift/proxy-server.conf`::