Docs: Fix order for PUT _mapping docs

Closes #8083

docs/reference/indices/put-mapping.asciidoc

@@ -6,7 +6,7 @@ specific type.
 
 [source,js]
 --------------------------------------------------
-$ curl -XPUT 'http://localhost:9200/twitter/tweet/_mapping' -d '
+$ curl -XPUT 'http://localhost:9200/twitter/_mapping/tweet' -d '
 {
     "tweet" : {
         "properties" : {
@@ -49,7 +49,7 @@ call, or even on `_all` the indices.
 
 [source,js]
 --------------------------------------------------
-$ curl -XPUT 'http://localhost:9200/kimchy,elasticsearch/tweet/_mapping' -d '
+$ curl -XPUT 'http://localhost:9200/kimchy,elasticsearch/_mapping/tweet' -d '
 {
     "tweet" : {
         "properties" : {
@@ -80,4 +80,3 @@ where
 
 
 Instead of `_mapping` you can also use the plural `_mappings`.
-The uri `PUT /{index}/{type}/_mapping` is still supported for backwards compatibility.  

docs/reference/mapping/dynamic-mapping.asciidoc

@@ -39,7 +39,7 @@ disables dynamic field creation for a `tweet`:
 
 [source,js]
 --------------------------------------------------
-$ curl -XPUT 'http://localhost:9200/twitter/tweet/_mapping' -d '
+$ curl -XPUT 'http://localhost:9200/twitter/_mapping/tweet' -d '
 {
     "tweet" : {
         "dynamic": "strict",
@@ -76,4 +76,3 @@ chance that the wrong field type will be used.
 This requirement can be disabled by setting
 `index.query.parse.allow_unmapped_fields` to `true`, in which case you run the
 risk that your query or filter might not work correctly.
-

docs/reference/search/suggesters/context-suggest.asciidoc

@@ -17,7 +17,7 @@ For instance:
 
 [source,js]
 --------------------------------------------------
-PUT services/service/_mapping
+PUT services/_mapping/service
 {
     "service": {
         "properties": {
@@ -315,4 +315,3 @@ POST services/_suggest
     }
 }
 --------------------------------------------------
-