Make sure you have checked _all_ steps below. ### Jira
- [x] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR" - https://issues.apache.org/jira/browse/AIRFLOW-XXX - In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-XXX\], code changes always need a Jira issue. ### Description - [x] Here are some details about my PR, including screenshots of any UI changes: **1. A wrong sample bash command** https://airflow.incubator.apache.org/howto/secure-connections.html <img width="797" alt="screen shot 2018-09-20 at 9 46 32 am" src="https://user-images.githubusercontent.com/11539188/45790992-2ece2180-bcba-11e8-8f19-4737efcf29da.png"> This sample bash command for sure would not work. It should be `export AIRFLOW__CORE__FERNET_KEY=your_fernet_key` (lowercase 'export' and no spaces around `=`) **2. A display issue** https://airflow.incubator.apache.org/kubernetes.html?highlight=kubernetes <img width="766" alt="screen shot 2018-09-20 at 9 47 00 am" src="https://user-images.githubusercontent.com/11539188/45790988-2c6bc780-bcba-11e8-9e73-d2e09e527fb0.png"> There are two items, `-Dags` and `-Logs`. But because an empty line is missing in the RST file, this part is not displayed correctly. **3. A few typos** A few other typos in different sections. ### Tests - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: Only documentation change. ### Commits - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 1. Subject is limited to 50 characters (not including Jira issue reference) 1. Subject does not end with a period 1. Subject uses the imperative mood ("add", not "adding") 1. Body wraps at 72 characters 1. Body explains "what" and "why", not "how" ### Documentation - [ ] In case of new functionality, my PR adds documentation that describes how to use it. - When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added. ### Code Quality - [ ] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff` [ Full content available at: https://github.com/apache/incubator-airflow/pull/3924 ] This message was relayed via gitbox.apache.org for [email protected]
