Bug Description

In keystone curl example document, it uses "curl -d '{"auth":{"passwordCredentials":{"username": "joeuser", "password": "secrete"}}}' -H "Content-type: application/json" http://localhost:35357/v2.0/tokens" to get a token, and in next example, it uses a token to access other service.

Actually without a tenantName in curl body of the first example, the token we get could be used to access other service directly. I think in this example, we could add tenantName in it. It is more meaningful in whole context.

In the keystone api_curl_examples document, the curl example for
"POST /tokens" did not specify a tenant. This example utilized
the default tenant, which is not commonly used. Changed the
example to include "tenantName" as part of the example to prevent
future confusion.