misc 1.8.10 updates

content/chronograf/v1.8/about_the_project/release-notes-changelog.md

@@ -30,7 +30,7 @@ USE "db_name"; DELETE FROM "measurement_name" WHERE "tag" = 'value' AND time < '
 - Repair dashboard import to remap sources in variables.
 - UI updates:
   - Ignore databases that cannot be read. Now, the Admin page correctly displays all databases the user has permissions to.
-  - Improve Send to Dashboard feedback on Data Explorer page.
+  - Improve Send to Dashboard feedback on the Data Explorer page.
 - Log Viewer updates:
   - Avoid endless networking loop.
   - Show timestamp with full nanosecond precision.

content/chronograf/v1.8/introduction/installation.md

@@ -70,7 +70,7 @@ sudo yum localinstall chronograf-<version#>.x86_64.rpm
 2. Fill out the form with the following details:
   * **Connection String**: Enter the hostname or IP of the machine that InfluxDB is running on, and be sure to include InfluxDB's default port `8086`.
   * **Connection Name**: Enter a name for your connection string.
-  * **Username** and **Password**: These fields can remain blank unless you've [enabled authentication](/influxdb/v1.8/administration/authentication_and_authorization) in InfluxDB.
+  * **Username** and **Password**: These fields can remain blank unless you've [enabled authentication](/influxdb/v1.8/administration/authentication_and_authorization) in InfluxDB. Chronograf user accounts and credentials should be different than credentials used for InfluxDB, to ensure distinct permissions can be applied. For example, you may want to set up a Chronograf to run as a service account with read-only permissions to InfluxDB. For more information, see how to [manage InfluxDB users in Chronograf] and [manage Chronograf users](/chronograf/v1.8/administration/managing-chronograf-users/).
   * **Telegraf Database Name**: Optionally, enter a name for your Telegraf database. The default name is Telegraf.
 3. Click **Add Source**.
 

content/influxdb/v1.8/query_language/manage-database.md

@@ -121,11 +121,6 @@ If you attempt to drop a database that does not exist, InfluxDB does not return
 The `DROP SERIES` query deletes all points from a [series](/influxdb/v1.8/concepts/glossary/#series) in a database,
 and it drops the series from the index.
 
-> **Note:** `DROP SERIES` does not support time intervals in the `WHERE` clause.
-See
-[`DELETE`](/influxdb/v1.8/query_language/manage-database/#delete-series-with-delete)
-for that functionality.
-
 The query takes the following form, where you must specify either the `FROM` clause or the `WHERE` clause:
 ```sql
 DROP SERIES FROM <measurement_name[,measurement_name]> WHERE <tag_key>='<tag_value>'
@@ -153,11 +148,9 @@ A successful `DROP SERIES` query returns an empty result.
 The `DELETE` query deletes all points from a
 [series](/influxdb/v1.8/concepts/glossary/#series) in a database.
 Unlike
-[`DROP SERIES`](/influxdb/v1.8/query_language/manage-database/#drop-series-from-the-index-with-drop-series), it does not drop the series from the index and it supports time intervals
-in the `WHERE` clause.
+[`DROP SERIES`](/influxdb/v1.8/query_language/manage-database/#drop-series-from-the-index-with-drop-series), `DELETE` does not drop the series from the index.
 
-The query takes the following form where you must include either the `FROM`
-clause or the `WHERE` clause, or both:
+You must include either the `FROM` clause, the `WHERE` clause, or both:
 
 ```
 DELETE FROM <measurement_name> WHERE [<tag_key>='<tag_value>'] | [<time interval>]
@@ -173,9 +166,9 @@ Delete all data associated with the measurement `h2o_quality` and where the tag
 > DELETE FROM "h2o_quality" WHERE "randtag" = '3'
 ```
 
-Delete all data in the database that occur before January 01, 2016:
+Delete all data in the database that occur before January 01, 2020:
 ```
-> DELETE WHERE time < '2016-01-01'
+> DELETE WHERE time < '2020-01-01'
 ```
 
 A successful `DELETE` query returns an empty result.