Moved disabling history docs to new section

It didn't really fit under the "Querying History" section.

Author: ddabble

CHANGES.rst

@@ -18,6 +18,8 @@ Unreleased
 **Fixes and improvements:**
 
 - Improved performance of the ``latest_of_each()`` history manager method (gh-1360)
+- Moved the "Save without creating historical records" subsection of "Querying History"
+  in the docs to a new section: "Disable Creating Historical Records" (gh-1387)
 
 3.7.0 (2024-05-29)
 ------------------

docs/disabling_history.rst

@@ -0,0 +1,51 @@
+Disable Creating Historical Records
+===================================
+
+Save without creating historical records
+----------------------------------------
+
+If you want to save model objects without triggering the creation of any historical
+records, you can do the following:
+
+.. code-block:: python
+
+    poll.skip_history_when_saving = True
+    poll.save()
+    # We recommend deleting the attribute afterward
+    del poll.skip_history_when_saving
+
+This also works when creating an object, but only when calling ``save()``:
+
+.. code-block:: python
+
+    # Note that `Poll.objects.create()` is not called
+    poll = Poll(question="Why?")
+    poll.skip_history_when_saving = True
+    poll.save()
+    del poll.skip_history_when_saving
+
+.. note::
+    Historical records will always be created when calling the ``create()`` manager method.
+
+Alternatively, call the ``save_without_historical_record()`` method on each object
+instead of ``save()``.
+This method is automatically added to a model when registering it for history-tracking
+(i.e. defining a ``HistoricalRecords``  manager field on the model),
+and it looks like this:
+
+.. code-block:: python
+
+    def save_without_historical_record(self, *args, **kwargs):
+        self.skip_history_when_saving = True
+        try:
+            ret = self.save(*args, **kwargs)
+        finally:
+            del self.skip_history_when_saving
+        return ret
+
+Or disable the creation of historical records for *all* models
+by adding the following line to your settings:
+
+.. code-block:: python
+
+    SIMPLE_HISTORY_ENABLED = False

docs/index.rst

@@ -66,6 +66,7 @@ Documentation
    admin
    historical_model
    user_tracking
+   disabling_history
    signals
    history_diffing
    multiple_dbs

docs/querying_history.rst

@@ -175,56 +175,6 @@ model history.
     <Poll: Poll object as of 2010-10-25 18:04:13.814128>
 
 
-Save without creating historical records
-----------------------------------------
-
-If you want to save model objects without triggering the creation of any historical
-records, you can do the following:
-
-.. code-block:: python
-
-    poll.skip_history_when_saving = True
-    poll.save()
-    # We recommend deleting the attribute afterward
-    del poll.skip_history_when_saving
-
-This also works when creating an object, but only when calling ``save()``:
-
-.. code-block:: python
-
-    # Note that `Poll.objects.create()` is not called
-    poll = Poll(question="Why?")
-    poll.skip_history_when_saving = True
-    poll.save()
-    del poll.skip_history_when_saving
-
-.. note::
-    Historical records will always be created when calling the ``create()`` manager method.
-
-Alternatively, call the ``save_without_historical_record()`` method on each object
-instead of ``save()``.
-This method is automatically added to a model when registering it for history-tracking
-(i.e. defining a ``HistoricalRecords``  manager field on the model),
-and it looks like this:
-
-.. code-block:: python
-
-    def save_without_historical_record(self, *args, **kwargs):
-        self.skip_history_when_saving = True
-        try:
-            ret = self.save(*args, **kwargs)
-        finally:
-            del self.skip_history_when_saving
-        return ret
-
-Or disable the creation of historical records for *all* models
-by adding the following line to your settings:
-
-.. code-block:: python
-
-    SIMPLE_HISTORY_ENABLED = False
-
-
 Filtering data using a relationship to the model
 ------------------------------------------------