chore(Influxdb-v1): Revise database initialization section

Author: jstirnaman

influxdb/content.md

@@ -573,24 +573,26 @@ Or run the influx client in a separate container:
 docker run --rm --link=influxdb -it %%IMAGE%%:1.8 influx -host influxdb
 ```
 
-Database Initialization
------------------------
+InfluxDB v1 database initialization
+-----------------------------------
 
-The InfluxDB image contains some extra functionality for initializing a database. These options are not suggested for production, but are quite useful when running standalone instances for testing.
+The InfluxDB Docker Hub image lets you set initialization options when creating an InfluxDB v1 container.
 
-The database initialization script will only be called when running `influxd`. It will not be executed when running any other program.
+**WARNING**: We **don't** recommend using these options for production scenarios, but they're useful when running standalone instances for testing.
 
-### Environment Variables
+The database initialization script is only called when running `influxd`.
 
-The InfluxDB image uses several environment variables to automatically configure certain parts of the server. They may significantly aid you in using this image.
+### Environment variables
+
+During the InfluxDB v1 set up process, the InfluxDB image uses environment variables to automatically configure some server options. You can override the following environment variables to customize set up options.
 
 #### INFLUXDB_DB
 
 Automatically initializes a database with the name of this environment variable.
 
 #### INFLUXDB_HTTP_AUTH_ENABLED
 
-Enables authentication. Either this must be set or `auth-enabled = true` must be set within the configuration file for any authentication related options below to work.
+Enables authentication. Either this must be set or `auth-enabled = true` must be set within the configuration file for any authentication-related options below to work.
 
 #### INFLUXDB_ADMIN_USER
 
@@ -634,11 +636,13 @@ To manually initialize the database and exit, the `/init-influxdb.sh` script can
 
 ```console
 docker run --rm \
-   -e INFLUXDB_DB=db0 \
-   -e INFLUXDB_ADMIN_USER=admin -e INFLUXDB_ADMIN_PASSWORD=supersecretpassword \
-   -e INFLUXDB_USER=telegraf -e INFLUXDB_USER_PASSWORD=secretpassword \
-   -v $PWD:/var/lib/influxdb \
-   %%IMAGE%%:1.8 /init-influxdb.sh
+    -e INFLUXDB_DB=db0 \
+    -e INFLUXDB_ADMIN_USER=admin \
+    -e INFLUXDB_ADMIN_PASSWORD=supersecretpassword \
+    -e INFLUXDB_USER=telegraf -e \
+    -e INFLUXDB_USER_PASSWORD=secretpassword \
+    -v $PWD:/var/lib/influxdb \
+    %%IMAGE%%:1.8 /init-influxdb.sh
 ```
 
 The above would create the database `db0`, create an admin user with the password `supersecretpassword`, then create the `telegraf` user with your telegraf's secret password. It would then exit and leave behind any files it created in the volume that you mounted.