Context Navigation

Changes between Initial Version and Version 1 of Ticket #31203

-              initial
+              v1
 Not 100% positive this is a bug, but definitely a breaking change in Django.
 In 1.11 ValidationError used force_text to stringify its messages, but in 2.2 and 3.0, it's using str.
+In 1.11 `ValidationError` used `force_text` to stringify its messages, but in 2.2 and 3.0, it's using `str`.
 force_text used to check for subtypes of six.text_type and let those through unchanged, whereas str forces the __str__ conversion.
+`force_text` used to check for subtypes of `six.text_type` and let those through unchanged, whereas str forces the `__str__` conversion.
 This interacts poorly with Markup, which 'unwraps' itself in the __str__ method. Here's a sample problem:
+This interacts poorly with Markup, which 'unwraps' itself in the `__str__` method. Here's a sample problem:
 …
 That error should render on a form as a span followed by some text; however, the use of str causes the 'safeness' of the markup to be lost and thus it's re-escaped and the HTML leaks into the page.
 Maybe Markup should be returning self in __str__, since it's a __str__ subclass. This bug can be worked around from client code using something like this:
+Maybe Markup should be returning self in `__str__`, since it's a `__str__` subclass. This bug can be worked around from client code using something like this: