Added controller indicator. Fixed formatting

Author: evilnick

src/en/controllers.md

@@ -2,16 +2,14 @@ Title: Juju Controllers
 TODO:  Figure out the 'block command' situation (including CLI help
          text). See 'Restricting command usage' section. The old page lives on.
        Need examples for each command.
-       Figure out how to present those examples due to the foldout bug not
-         allowing syntax highlighting. So far, under 'Creating a controller'
-         there is a link to the old creating page.
+       .
 
 
 # Controllers
 
 A Juju *controller* is the management node of a Juju cloud environment. In
 particluar, it houses the database and keeps track of all the models in that
-environment. Although it is a special node, it is nonetheless a machine that
+environment. Although it is a special node, it is a machine that
 gets created by Juju (during the "bootstrap" stage) and, in that sense, is
 similar to other Juju machines.
 
@@ -20,13 +18,13 @@ and the 'default' model. The primary purpose of the 'controller' model is to
 run and manage the Juju API server and the underlying database. Additional
 models may be created by the user - see [Models](./models.html).
 
-When a controller is intended to be used by multiple people, it is recommended
-that Juju's [multi-user functionality](./users.html) be leveraged.
-
 Since a controller can host multiple models, the destruction of a controller
 must be done with ample consideration since all its models will be destroyed
 along with it.
 
+In some circumstances you may wish to share a controller or one of its associated
+models. Juju provides [multi-user functionality](./users.html) for this purpose.
+
 
 ## Controller management
 
@@ -62,7 +60,9 @@ Common controller management tasks are summarized below.
    Use the `juju list-controllers` command to list all controllers knowable by
    the current system user.
 
-   `juju list-controllers [options]`
+         juju list-controllers [options] 
+   
+   The currently active controller is indicated in the list with an asterisk('*').
 
    For complete explanation, syntax and examples see the
    [command reference page](./commands.html#list-controllers) or the `juju help
@@ -76,7 +76,7 @@ Common controller management tasks are summarized below.
    Information includes UUID, API endpoints, certificates, and bootstrap
    configuarion.
 
-   `juju show-controller [options]`
+         juju show-controller [options]
 
    For complete explanation, syntax and examples see the
    [command reference page](./commands.html#show-controller) or the `juju help
@@ -88,7 +88,7 @@ Common controller management tasks are summarized below.
 
    Use the `juju destroy-controller` command to remove a controller.
 
-   `juju destroy-controller [options]`
+         juju destroy-controller [options]
 
    For complete explanation, syntax and examples see the
    [command reference page](./commands.html#destroy-controller) or the `juju help
@@ -104,7 +104,7 @@ Common controller management tasks are summarized below.
    of the `juju destroy-controller` command and failover to the more drastic
    behaviour if that attempt fails.
 
-   `juju kill-controller [options]`
+         juju kill-controller [options]
 
    For complete explanation, syntax and examples see the
    [command reference page](./commands.html#kill-controller) or the `juju help