Fix rst grammar problems (#4116)

docs/faq.rst

@@ -46,10 +46,10 @@ https://github.com/airbnb/superset/issues?q=label%3Aexample+is%3Aclosed
 
 
 Can I upload and visualize csv data?
--------------------------------------
+------------------------------------
 
 Yes, using the ``Upload a CSV`` button under the ``Sources``
-menu item. This brings up a form that allows you specify required information. After creating the table from CSV, it can then be loadede like any other on the ``Sources -> Tables``page.
+menu item. This brings up a form that allows you specify required information. After creating the table from CSV, it can then be loaded like any other on the ``Sources -> Tables``page.
 
 
 Why are my queries timing out?
@@ -106,7 +106,7 @@ edit the ``JSON Metadata`` field, more specifically the
 never be affected by any dashboard level filtering.
 
 
-..code::
+..code:: json
 
     {
         "filter_immune_slices": [324, 65, 92],
@@ -141,7 +141,7 @@ to be refreshed - especially if some data is slow moving, or run heavy queries.
 slices from the timed refresh process, add the ``timed_refresh_immune_slices`` key to the dashboard
 ``JSON Metadata`` field:
 
-..code::
+..code:: json
 
     {
        "filter_immune_slices": [],
@@ -157,7 +157,7 @@ Slice refresh will also be staggered over the specified period. You can turn off
 by setting the ``stagger_refresh`` to ``false`` and modify the stagger period by setting
 ``stagger_time`` to a value in milliseconds in the ``JSON Metadata`` field:
 
-..code::
+..code:: json
 
     {
         "stagger_refresh": false,
@@ -236,11 +236,11 @@ It is possible on a per-dashboard basis by providing a mapping of
 labels to colors in the ``JSON Metadata`` attribute using the
 ``label_colors`` key.
 
-..code::
+..code:: json
 
-	{
-	  "label_colors": {
-		"Girls": "#FF69B4",
-		"Boys": "#ADD8E6"
-	  }
-	}
+    {
+        "label_colors": {
+            "Girls": "#FF69B4",
+            "Boys": "#ADD8E6"
+        }
+    }

docs/import_export_datasources.rst

@@ -72,7 +72,7 @@ In order to import datasources from a YAML file(s), run: ::
     superset import_datasources -p <path or filename>
 
 If you supply a path all files ending with ``*.yaml`` or ``*.yml`` will be parsed.
-You can apply additional falgs e.g.: ::
+You can apply additional flags e.g.: ::
 
     superset import_datasources -p <path> -r
 

docs/index.rst

@@ -25,10 +25,10 @@ intelligence web application
     endorsed by the ASF.
 
 Overview
-=======================================
+========
 
 Features
----------
+--------
 
 - A rich set of data visualizations
 - An easy-to-use interface for exploring and visualizing data
@@ -61,7 +61,7 @@ Features
 
 
 Contents
----------
+--------
 
 .. toctree::
     :maxdepth: 2

docs/installation.rst

@@ -148,7 +148,7 @@ around `gunicorn`, it doesn't expose all the options you may need,
 so you'll want to craft your own `gunicorn` command in your production
 environment. Here's an **async** setup known to work well: ::
 
-	gunicorn \
+ 　gunicorn \
 		-w 10 \
 		-k gevent \
 		--timeout 120 \
@@ -185,7 +185,7 @@ In case that the reverse proxy is used for providing ssl encryption,
 an explicit definition of the `X-Forwarded-Proto` may be required.
 For the Apache webserver this can be set as follows: ::
 
-    RequestHeader set X-Forwarded-Proto "https"
+　RequestHeader set X-Forwarded-Proto "https"
 
 Configuration
 -------------
@@ -399,7 +399,7 @@ metadata from your Druid cluster(s)
 
 
 CORS
------
+----
 
 The extra CORS Dependency must be installed:
 

docs/security.rst

@@ -10,7 +10,7 @@ Provided Roles
 --------------
 Superset ships with a set of roles that are handled by Superset itself.
 You can assume that these roles will stay up-to-date as Superset evolves.
-Even though it's possible for ``Admin`` usrs to do so, it is not recommended
+Even though it's possible for ``Admin`` users to do so, it is not recommended
 that you alter these roles in any way by removing
 or adding permissions to them as these roles will be re-synchronized to
 their original values as you run your next ``superset init`` command.

docs/sqllab.rst

@@ -65,7 +65,7 @@ Superset's Jinja context:
 Extending macros
 ''''''''''''''''
 
-As mentioned in the `Installation & Configuration`_ documentation,
+As mentioned in the `Installation & Configuration <https://superset.incubator.apache.org/installation.html#installation-configuration>`_ documentation,
 it's possible for administrators to expose more more macros in their
 environment using the configuration variable ``JINJA_CONTEXT_ADDONS``.
 All objects referenced in this dictionary will become available for users