Fix doc comments for new enforce default flag

This commit fixes the review comments from
patch - https://review.opendev.org/#/c/717943/

Change-Id: I00edbea503aefbce31cbb43a74929db752235bf0

1 files changed, 6 insertions, 6 deletions

diff --git a/releasenotes/notes/enforce_new_defaults-6ae17d8b8d166a2c.yaml b/releasenotes/notes/enforce_new_defaults-6ae17d8b8d166a2c.yaml
index 8ff851f..4a537de 100644
--- a/releasenotes/notes/enforce_new_defaults-6ae17d8b8d166a2c.yaml
+++ b/releasenotes/notes/enforce_new_defaults-6ae17d8b8d166a2c.yaml
@@ -3,9 +3,9 @@ features:
     A new configuration option ``enforce_new_defaults`` has been
     added to the ``[oslo_policy]`` group to control whether or not to
     use the old deprecated defaults. If ``True``, the old deprecated
-    defaults are not going to be evaluated which mean if any existing
-    token allowed for old defaults but disallowed for new defaults
-    will be disallowed. It is encouraged to enable this flag along
-    with ``enforce_scope`` flag so that you can get benefits of new
-    defaults and ``scope_type`` together. This way operators can switch
-    to new defaults without overwriting the rule in policy file.
+    defaults are not going to be evaluated which means if any existing
+    token is allowed for old defaults but disallowed for new defaults
+    it will be disallowed. It is encouraged to enable this flag along
+    with the ``enforce_scope`` flag so that you can get the benefits of
+    new defaults and ``scope_type`` together. This way operators can switch
+    to new defaults without overwriting the rules in the policy file.