[4.2.x] Added missing backticks in docs.

Backport of 02376f1f53 from main

docs/ref/models/options.txt

@@ -445,7 +445,7 @@ not be looking at your Django code. For example::
         unique_together = ["driver", "restaurant"]
 
     A :class:`~django.db.models.ManyToManyField` cannot be included in
-    unique_together. (It's not clear what that would even mean!) If you
+    ``unique_together``. (It's not clear what that would even mean!) If you
     need to validate uniqueness related to a
     :class:`~django.db.models.ManyToManyField`, try using a signal or
     an explicit :attr:`through <ManyToManyField.through>` model.

docs/releases/1.8.2.txt

@@ -48,8 +48,9 @@ Bugfixes
 
 * Fixed ``isnull`` lookup for ``HStoreField`` (:ticket:`24751`).
 
-* Fixed a MySQL crash when a migration removes a combined index (unique_together
-  or index_together) containing a foreign key (:ticket:`24757`).
+* Fixed a MySQL crash when a migration removes a combined index (
+  ``unique_together`` or ``index_together``) containing a foreign key
+  (:ticket:`24757`).
 
 * Fixed session cookie deletion when using :setting:`SESSION_COOKIE_DOMAIN`
   (:ticket:`24799`).

docs/topics/db/transactions.txt

@@ -666,7 +666,7 @@ will fail with the error "current transaction is aborted, queries ignored
 until end of transaction block". While the basic use of ``save()`` is unlikely
 to raise an exception in PostgreSQL, there are more advanced usage patterns
 which might, such as saving objects with unique fields, saving using the
-force_insert/force_update flag, or invoking custom SQL.
+``force_insert``/``force_update`` flag, or invoking custom SQL.
 
 There are several ways to recover from this sort of error.