fix some docs warnings

Author: reint-fischer

docs/development/policies.md

@@ -10,7 +10,7 @@ We accept that Parcels developers have their own motivation for using (or not us
 
 Remember that reviews are done by human maintainers - asking us to review code that an AI wrote but you don't understand isn't kind to these maintainers.
 
-The [CLAUDE.md](/CLAUDE.md) file in the repository has additional instructions for AI agents to follow when contributing to Parcels.
+The [CLAUDE.md](https://github.com/Parcels-code/Parcels/blob/HEAD/CLAUDE.md) file in the repository has additional instructions for AI agents to follow when contributing to Parcels.
 
 ## Versioning
 

src/parcels/_core/field.py

@@ -54,30 +54,34 @@ class Field:
     """The Field class that holds scalar field data.
     The `Field` object is a wrapper around a xarray.DataArray or uxarray.UxDataArray object.
     Additionally, it holds a dynamic Callable procedure that is used to interpolate the field data.
-    During initialization, the user is required to supply a custom interpolation method that is used to interpolate the field data,
-    so long as the interpolation method has the correct signature.
+    During initialization, the user is required to supply a custom interpolation method that is used 
+    to interpolate the field data, so long as the interpolation method has the correct signature.
 
     Notes
     -----
     The xarray.DataArray or uxarray.UxDataArray object contains the field data and metadata.
-        * dims: (time, [nz1 | nz], [face_lat | node_lat | edge_lat], [face_lon | node_lon | edge_lon])
-        * attrs: (location, mesh, mesh)
 
-    When using a xarray.DataArray object,
+    * dims: (time, [nz1 | nz], [face_lat | node_lat | edge_lat], [face_lon | node_lon | edge_lon])
+    * attrs: (location, mesh, mesh)
+
+    When using a xarray.DataArray object:
+        
     * The xarray.DataArray object must have the "location" and "mesh" attributes set.
-    * The "location" attribute must be set to one of the following to define which pairing of points a field is associated with.
-       * "node"
-       * "face"
-       * "x_edge"
-       * "y_edge"
-    * For an A-Grid, the "location" attribute must be set to / is assumed to be "node" (node_lat,node_lon).
+    * The "location" attribute must be set to one of the following to define which pairing of points a field is associated with:
+        * "node"
+        * "face"
+        * "x_edge"
+        * "y_edge"
+
+    * For an A-Grid, the "location" attribute must be set to / is assumed to be "node" (node_lat,node_lon). 
     * For a C-Grid, the "location" setting for a field has the following interpretation:
         * "node" ~> the field is associated with the vorticity points (node_lat, node_lon)
         * "face" ~> the field is associated with the tracer points (face_lat, face_lon)
         * "x_edge" ~> the field is associated with the u-velocity points (face_lat, node_lon)
         * "y_edge" ~> the field is associated with the v-velocity points (node_lat, face_lon)
 
-    When using a uxarray.UxDataArray object,
+    When using a uxarray.UxDataArray object:
+
     * The uxarray.UxDataArray.UxGrid object must have the "Conventions" attribute set to "UGRID-1.0"
       and the uxarray.UxDataArray object must comply with the UGRID conventions.
       See https://ugrid-conventions.github.io/ugrid-conventions/ for more information.