Removed -fs from troubleshooting command (#4177)

* Removed -fs from troubleshooting command

* Add YAML file for configmaps in concepts

* Add new topic for configmaps in concepts

* Add configuration entry for understanding configmaps

* Move Understanding Configmaps to a separate concept file

* Revert "Move Understanding Configmaps to a separate concept file"

This reverts commit 71bd80d.

* Revert "Add configuration entry for understanding configmaps"

This reverts commit c27fc13.

* Revert "Add new topic for configmaps in concepts"

This reverts commit 3d535f5.

* Revert "Add YAML file for configmaps in concepts"

This reverts commit 8ecabd6.

docs/tasks/administer-cluster/configure-upgrade-etcd.md

@@ -35,7 +35,7 @@ see _some doc_.
 
   Performance and stability of the cluster is sensitive to network and disk IO. Any resource starvation can lead to heartbeat timeout, causing instability of the cluster. An unstable etcd indicates that no leader is elected. Under such circumstances, a cluster cannot make any changes to its current state, which implies no new pods can be scheduled.
 
-* Keeping stable etcd clusters is critical to the stability of Kubernetes clusters. Therefore, run etcd clusters on dedicated machines or isolated environments for [guaranteed resource requirements](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/hardware.md#hardware-recommendations). 
+* Keeping stable etcd clusters is critical to the stability of Kubernetes clusters. Therefore, run etcd clusters on dedicated machines or isolated environments for [guaranteed resource requirements](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/hardware.md#hardware-recommendations).
 
 ## Resource requirements
 
@@ -403,5 +403,5 @@ test key. On your master VM (or somewhere with firewalls configured such that
 you can talk to your cluster's etcd), try:
 
 ```shell
-curl -fs -X PUT "http://${host}:${port}/v2/keys/_test"
+curl -X PUT "http://${host}:${port}/v2/keys/_test"
 ```