Add reference to rename endpoint in correct version & add to new

Docker-DCO-1.1-Signed-off-by: Jessica Frazelle <jess@docker.com> (github: jfrazelle)

docs/sources/reference/api/docker_remote_api.md

@@ -56,6 +56,11 @@ Docker client now hints potential proxies about connection hijacking using HTTP
 **New!**
 This endpoint now returns the list current execs associated with the container (`ExecIDs`).
 
+`POST /containers/(id)/rename`
+
+**New!**
+New endpoint to rename a container `id` to a new name.
+
 ## v1.16
 
 ### Full Documentation

docs/sources/reference/api/docker_remote_api_v1.15.md

@@ -647,27 +647,6 @@ Status Codes:
 -   **404** – no such container
 -   **500** – server error
 
-### Rename a container
-
-`POST /containers/(id)/rename/(new_name)`
-
-Rename the container `id` to a `new_name`
-
-**Example request**:
-
-        POST /containers/e90e34656806/rename/new_name HTTP/1.1
-
-**Example response**:
-
-        HTTP/1.1 204 No Content
-
-Status Codes:
-
--   **204** – no error
--   **404** – no such container
--   **409** - conflict name already assigned
--   **500** – server error
-
 ### Pause a container
 
 `POST /containers/(id)/pause`

docs/sources/reference/api/docker_remote_api_v1.17.md

@@ -599,6 +599,31 @@ Status Codes:
 -   **404** – no such container
 -   **500** – server error
 
+### Rename a container
+
+`POST /containers/(id)/rename`
+
+Rename the container `id` to a `new_name`
+
+**Example request**:
+
+        POST /containers/e90e34656806/rename?name=new_name HTTP/1.1
+
+**Example response**:
+
+        HTTP/1.1 204 No Content
+
+Query Parameters:
+
+-   **name** – new name for the container
+
+Status Codes:
+
+-   **204** – no error
+-   **404** – no such container
+-   **409** - conflict name already assigned
+-   **500** – server error
+
 ### Pause a container
 
 `POST /containers/(id)/pause`