Apply suggestions from code review

clarify confusing text

Signed-off-by: Tariq Kurd <tariqandlaura@gmail.com>

Author: tariqkurd-repo

src/insns/acperm_32bit.adoc

@@ -59,8 +59,8 @@ The rules from <<acperm_rules>> must be followed when removing permissions.
 The behaviour of currently illegal combinations from <<acperm_rules>> is to clear the permission if invalid (or in the case of <<sl_perm>> set it to 0 (_local_)).
 
 * For RV64 all such combinations may be redefined by future extensions.
-* For the RV32 only rules none of these combinations are possible to meet the encoding requirements for <<cap_perms_encoding32>>, or
-<<cap_perms_encoding_levels32>> if <<cheri_levels_ext,{cheri_levels_ext_name}>> is implemented. In all cases invalid permissions are cleared.
+* The RV32 only rules are added because they remove combinations which do not meet the encoding requirements for <<cap_perms_encoding32>>, or
+<<cap_perms_encoding_levels32>> if <<cheri_levels_ext,{cheri_levels_ext_name}>> is implemented.
 
 .Capability permissions bit field
 [#acperm_bit_field]