fix doc references

Author: jakkdl

docs/changelog.rst

@@ -6,7 +6,7 @@ Changelog
 
 24.11.3
 =======
-- Revert :ref:`ASYNC100 <async100>` ignoring :func:`trio.open_nursery` and :func:`anyio.create_task_group` due to it not viewing `start_soon()` as introducing a :ref:`cancel point`.
+- Revert :ref:`ASYNC100 <async100>` ignoring :func:`trio.open_nursery` and :func:`anyio.create_task_group` due to it not viewing `start_soon()` as introducing a :ref:`cancel point <cancel_point>`.
 
 24.11.2
 =======
@@ -15,8 +15,8 @@ Changelog
 24.11.1
 =======
 - :ref:`ASYNC100 <async100>` now ignores :func:`trio.open_nursery` and :func:`anyio.create_task_group`
-  as cancellation sources, because they are :ref:`schedule points <schedule_points>` but not
-  :ref:`cancellation points <cancel_points>`.
+  as cancellation sources, because they are :ref:`schedule points <schedule_point>` but not
+  :ref:`cancellation points <cancel_point>`.
 - :ref:`ASYNC101 <async101>` and :ref:`ASYNC119 <async119>` are now silenced for decorators in :ref:`transform-async-generator-decorators`.
 
 24.10.2

docs/glossary.rst

@@ -99,7 +99,7 @@ functions defined by Trio will either checkpoint or raise an exception when
 iteration, and when exhausting the iterator, and ``async with`` will checkpoint
 on at least one of enter/exit.
 
-The one exception is :func:`trio.open_nursery` and :func:`anyio.create_task_group` which are :ref:`schedule_points` but not :ref:`cancel_points`.
+The one exception is :func:`trio.open_nursery` and :func:`anyio.create_task_group` which are :ref:`schedule points <schedule_point>` but not :ref:`cancel points <cancel_point>`.
 
 asyncio does not place any guarantees on if or when asyncio functions will
 checkpoint. This means that enabling and adhering to :ref:`ASYNC91x <ASYNC910>`
@@ -117,7 +117,6 @@ To insert a checkpoint with no other side effects, you can use
 <asyncio.sleep>`
 
 .. _schedule_point:
-.. _schedule_points:
 
 Schedule Point
 --------------
@@ -137,7 +136,6 @@ asyncio does not have any direct equivalents due to their cancellation model bei
 
 
 .. _cancel_point:
-.. _cancel_points:
 
 Cancel Point
 ------------