Collected markedown fixes around syntax.

examples/elasticsearch/README.md

@@ -111,7 +111,6 @@ metadata:
   namespace: NAMESPACE
 data:
   token: "TOKEN"
-
 ```
 
 Replace `NAMESPACE` with the actual namespace to be used and `TOKEN` with the basic64 encoded
@@ -126,7 +125,6 @@ $ kubectl config view
  ...   
 $ echo yGlDcMvSZPX4PyP0Q5bHgAYgi1iyEHv2 | base64
 eUdsRGNNdlNaUFg0UHlQMFE1YkhnQVlnaTFpeUVIdjIK=
-
 ```
 
 resulting in the file:
@@ -139,7 +137,6 @@ metadata:
   namespace: mytunes
 data:
   token: "eUdsRGNNdlNaUFg0UHlQMFE1YkhnQVlnaTFpeUVIdjIK="
-
 ```
 
 which can be used to create the secret in your namespace:
@@ -147,7 +144,6 @@ which can be used to create the secret in your namespace:
 ```console
 kubectl create -f examples/elasticsearch/apiserver-secret.yaml --namespace=mytunes
 secrets/apiserver-secret
-
 ```
 
 Now you are ready to create the replication controller which will then create the pods:
@@ -155,7 +151,6 @@ Now you are ready to create the replication controller which will then create th
 ```console
 $ kubectl create -f examples/elasticsearch/music-rc.yaml --namespace=mytunes
 replicationcontrollers/music-db
-
 ```
 
 It's also useful to have a [service](../../docs/user-guide/services.md) with an load balancer for accessing the Elasticsearch
@@ -184,7 +179,6 @@ Let's create the service with an external load balancer:
 ```console
 $ kubectl create -f examples/elasticsearch/music-service.yaml --namespace=mytunes
 services/music-server
-
 ```
 
 Let's see what we've got:
@@ -301,7 +295,6 @@ music-db-u1ru3   1/1       Running   0          38s
 music-db-wnss2   1/1       Running   0          1m
 music-db-x7j2w   1/1       Running   0          1m
 music-db-zjqyv   1/1       Running   0          1m
-
 ```
 
 Let's check to make sure that these 10 nodes are part of the same Elasticsearch cluster:
@@ -359,7 +352,6 @@ $ curl 104.197.12.157:9200/_nodes?pretty=true | grep name
           "name" : "mytunes-db"
         "vm_name" : "OpenJDK 64-Bit Server VM",
           "name" : "eth0",
-
 ```