Generalize release note for bug 1878938

This commit just addresses minor comments in the release note wording
for the original review:

	https://review.opendev.org/#/c/731087/10/releasenotes/notes/bug-1878938-70ee2af6fdf66004.yaml

Change-Id: I00aa074393b8498efde35d843fb0d05a209f2b5c

1 files changed, 6 insertions, 6 deletions

diff --git a/releasenotes/notes/bug-1878938-70ee2af6fdf66004.yaml b/releasenotes/notes/bug-1878938-70ee2af6fdf66004.yaml
index 37eddac1f..21a53b482 100644
--- a/releasenotes/notes/bug-1878938-70ee2af6fdf66004.yaml
+++ b/releasenotes/notes/bug-1878938-70ee2af6fdf66004.yaml
@@ -4,13 +4,13 @@ fixes:
     [`bug 1878938 <https://bugs.launchpad.net/keystone/+bug/1878938>`_]
     Previously when a user used to have system role assignment and tries to delete
     the same role, the system role assignments still existed in system_assignment
-    table. This fix ensures that deleting a role should delete all the its assignments
-    from every assignment table.
+    table. This causes keystone to return `HTTP 404 Not Found` errors when listing
+    role assignments with names (e.g., `--names` or `?include_names`).
 
-    If you are affected by this bug, a fix in the keystone database will be
-    needed so we recommend to remove the stale role assignmensts before doing this
-    process.
+    If you are affected by this bug, you must remove stale role assignments
+    manually. The following is an example SQL statement you can use to fix the
+    issue, but you should verify it's applicability to your deployment's SQL
+    implementation and version.
 
     SQL:
-         - delete from assignment where role_id not in (select id from role);
          - delete from system_assignment where role_id not in (select id from role);