Clarify some release notes prior to the 7.0.0 release

Change-Id: I55dc81659973ab5afc60b030b44f30e62b73dbd9

releasenotes/notes/clarify-project-id-variable-5832698315000438.yaml

@@ -1,13 +1,13 @@
 ---
 deprecations:
-  - keyword argument **tenant_id** of novaclient.client.Client entry-point was
+  - Keyword argument **tenant_id** of novaclient.client.Client entry-point was
-    deprecated in favor of **project_id**;
+    deprecated in favor of **project_id**.
-  - keyword argument **tenant_name** of novaclient.client.Client entry-point
+  - Keyword argument **tenant_name** of novaclient.client.Client entry-point
-    was deprecated in favor of **project_name**;
+    was deprecated in favor of **project_name**.
 other:
   - The meaning of 'project_id' variable of novaclient.client.Client
     entry-point was not clear. In different cases it was used as ID or Name of
-    project(in terms of Keystone). The time to identify meaning is come, so now
+    project (in terms of Keystone). The time to identify meaning is come, so
-    project_id/tenant_id variables specifically mean about Project ID(in terms
+    now project_id/tenant_id variables specifically mean Project ID (in terms
-    of Keystone) and project_name/tenant_name variables take care about Project
+    of Keystone) and project_name/tenant_name variables mean Project Name (in
-    Name(in terms of Keystone).
+    terms of Keystone).

releasenotes/notes/deprecate-proxy-args-a3f4e224f7664ff8.yaml

@@ -1,5 +1,5 @@
 ---
 deprecations:
-  - There are two arguments for proxying stuff (proxy_tenant_id and
+  - The **proxy_tenant_id** and **proxy_token** arguments to the
-    proxy_token) in novaclient.client.Client entry-point. They were never
+    novaclient.client.Client entry-point were never documented nor tested and
-    documented and tested.
+    are now deprecated for removal in a future release.

releasenotes/notes/microversion-v2_38-0618fe2b3c7f96f9.yaml

@@ -1,5 +1,5 @@
 ---
 upgrade:
   - Support for microversion 2.38 added. As of microversion 2.38, invalid
-    statuses passed to 'nova list --status invalid_status' will result in a
+    statuses passed to ``nova list --status invalid_status`` will result in a
     HTTP 400 Bad Request error response.

releasenotes/notes/rename-bypass-url-42cd96956a6bc6dc.yaml

@@ -3,8 +3,8 @@ deprecations:
   - The **--bypass-url** CLI argument was deprecated in favor of
     **--endpoint-override**
   - The **bypass_url** argument of novaclient.client.Client entry-point was
-    deprecated in favor of **endpoint_override**
+    deprecated in favor of **endpoint_override**.
 fixes:
-  - Inability to use bypass-url with keystone session
+  - Inability to use bypass-url with keystone session is fixed.
 features:
-  - You can use *bypass-url*/**endpoint-override** with Keystone V3
+  - You can use **bypass-url** / **endpoint-override** with Keystone V3.

releasenotes/notes/restrict-args-for-novaclient-ep-491098c3634365be.yaml

@@ -1,5 +1,8 @@
 ---
 upgrade:
-  - novaclient.client.Client entry-point accepts only 5 positional arguments(
+  - |
-    version, username, api_key, project_id, auth_url). Using positional
+    novaclient.client.Client entry-point accepts only 5 positional arguments::
-    arguments for all other options become an error.
+
+      version, username, api_key, project_id, auth_url
+
+    Using positional arguments for all other options is now an error.