style(Logs): Added minor TW edits

src/content/docs/logs/ui-data/parsing.mdx

@@ -1065,7 +1065,7 @@ To create and manage your own, custom parsing rules:
 3. Enter a name for the new parsing rule.
 4. Select an existing field to parse (default = `message`), or enter a new field name.
 5. Enter a valid NRQL `WHERE` clause to match the logs you want to parse.
-6. Select a matching log if one exists, or click on the <DoNotTranslate>**Paste log**</DoNotTranslate> tab to paste in a sample log.  Note that if you are copying text from the Logs UI or the Query Builder to paste into the parsing UI, ensure that it is the <DoNotTranslate>*Unformatted*</DoNotTranslate> version.
+6. Select a matching log if one exists, or click on the <DoNotTranslate>**Paste log**</DoNotTranslate> tab to paste in a sample log. Note that if you copy text from the logs UI or the query builder to paste into the parsing UI, ensure that it's the <DoNotTranslate>*Unformatted*</DoNotTranslate> version.
 7. Enter the parsing rule and validate it's working by viewing the results in the <DoNotTranslate>**Output**</DoNotTranslate> section. To learn about Grok and custom parsing rules, read [our blog post about how to parse logs with Grok patterns](https://blog.newrelic.com/product-news/how-to-use-grok-log-parsing).
 8. Enable and save the custom parsing rule.