Fix heading

Author: dvdoug

CHANGELOG.md

@@ -4,7 +4,7 @@
 
 ## [5.11.0] - 2025-06-15
 ### Added
-- Added new parameter `accuracy` and new method `getAccuracy()` on `Point` objects to store/reveal accuracy of the point.
+- Added new parameter `$accuracy` and new method `getAccuracy()` on `Point` objects to store/reveal accuracy of the point.
   You can use this either to store the data for your own use (e.g. survey errors) and/or PHPCoord will update this with
   the accuracy of the calculated point after a conversion
 ### Changed

docs/coordinate_conversions_easy.rst

@@ -78,12 +78,6 @@ between almost any two CRSs is possible as long as they have a common link.
     the target CRS). If you know a transformation should be possible, but PHPCoord cannot find it you may wish
     to try an explicit 2-stage conversion (e.g. source to WGS84, WGS84 to target).
 
-Accuracy
---------
-After a conversion, you can call ``getAccuracy()`` on the new point to reveal the fidelity of the conversion. PHPCoord
-will always pick the most accurate conversion it knows how to do.
-
-
 Boundaries
 ----------
 Every CRS has a defined area ("extent") over which it operates. Some are worldwide (e.g. WGS84), but most are regional
@@ -165,6 +159,9 @@ that conversions between CRSs are not just converting between mathematical ideal
 *sets of observations*. When this happens it means that the conversions between the CRSs can only ever be
 an approximation (typically within a few metres) rather than exact.
 
+After a conversion, you can call ``getAccuracy()`` on the new ``Point`` to reveal the fidelity of the conversion. PHPCoord
+will always pick the most accurate conversion it knows how to do.
+
 Extents
 ^^^^^^^
 When dealing with CRSs that cover significant land area it is possible (and common) for mapping agencies to derive