edits

Author: genwhittTTD

docs/getting-started/gs-normalization-encoding.md

@@ -211,18 +211,16 @@ You can use this tool to verify that your internal processes are set up to corre
 
 ## Troubleshooting
 
-If you're having trouble or getting errors, or even if you just want to be sure you're following the steps correctly, here are some things you can check:
+In all scenarios, follow the steps on your side to prepare your DII for processing, and then check your resulting values by using the [UID2 Hashing Tool](#uid2-hashing-tool). If the results don't match, check each step to find the error.
 
-- **Hashing tool**: In all scenarios, follow the steps on your side, and then check by using the [UID2 Hashing Tool](#uid2-hashing-tool). If the results don't match, check each step to find the error.
+If you're having trouble or getting errors, or even if you just want to be sure you're following the steps correctly, here are some things you can check:
 
 - **Phone numbers**: Make sure you're normalizing—and normalizing correctly—as the first step.
 
-  If you're processing emails, the service does the normalization; however, with phone numbers, the service cannot normalize. For example, it cannot determine a missing country code. Use these resources:
-  - For instructions, see [Phone Number Normalization](#phone-number-normalization).
-  - To cross-check, test using the [UID2 Hashing Tool](#uid2-hashing-tool).
+  The service normalizes emails, but it can't normalize phone numbers. For example, it can't determine the value for a missing country code. Use these resources:
+  - Instructions:  [Phone Number Normalization](#phone-number-normalization).
+  - Tool for cross-checking: [UID2 Hashing Tool](#uid2-hashing-tool).
 
 - **Use the Base64-encoded value**: The process includes normalizing, then hashing, then Base64-encoding the bytes of the hash value. When generating UID2s, the input is the Base64-encoded value. Make sure you're using this 44-character string value.
 
-- You might see the following error message: "The hashing value must be 44 characters." In this scenario, there is an error with the hashing function you are using. You must use the hex to Base64 encoding of the SHA-256 hash. For details, see [Email Address Hash Encoding](#email-address-hash-encoding) or [Phone Number Hash Encoding](#phone-number-hash-encoding).
-
-  To cross-check, test using the [UID2 Hashing Tool](#uid2-hashing-tool).
+- You might see the following error message: "The hashing value must be 44 characters." In this scenario, there is an error with the hashing function you're using. Use the hex to Base64 encoding of the SHA-256 hash. For details, see [Email Address Hash Encoding](#email-address-hash-encoding) or [Phone Number Hash Encoding](#phone-number-hash-encoding). To cross-check, test using the [UID2 Hashing Tool](#uid2-hashing-tool).