From 757dd707b6c47481ae21ec119cfb6b33ff49139a Mon Sep 17 00:00:00 2001
From: Oleg Shalygin <oshalygin@gmail.com>
Date: Wed, 4 Jan 2017 16:23:20 -0800
Subject: [PATCH] Update configs with username followed by password

The way that the document currently flows and how we typically perceive credentials, we usually set our username first followed by the password.

Seeing the configuration first set password then username seems counter-intuitive.  There is nothing wrong with the docs, it is just clearer to view username=>password.
---
 docs/user-guide/secrets/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/user-guide/secrets/index.md b/docs/user-guide/secrets/index.md
index 63a2a052ea..07764434fd 100644
--- a/docs/user-guide/secrets/index.md
+++ b/docs/user-guide/secrets/index.md
@@ -113,8 +113,8 @@ metadata:
   name: mysecret
 type: Opaque
 data:
-  password: MWYyZDFlMmU2N2Rm
   username: YWRtaW4=
+  password: MWYyZDFlMmU2N2Rm
 ```
 
 The data field is a map.  Its keys must match
@@ -142,8 +142,8 @@ Get back the secret created in the previous section:
 $ kubectl get secret mysecret -o yaml
 apiVersion: v1
 data:
-  password: MWYyZDFlMmU2N2Rm
   username: YWRtaW4=
+  password: MWYyZDFlMmU2N2Rm
 kind: Secret
 metadata:
   creationTimestamp: 2016-01-22T18:41:56Z