Chore: s/further reading.*/see also/

Reason: Modernize legacy wording and reduce AI slop.

Idea: Apply a consistent "naming things" like others are doing it,
consistently across the board.

https://learn.microsoft.com/en-us/dotnet/framework/data/adonet/#see-also
https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/#see-also
https://learn.microsoft.com/en-us/dotnet/framework/tools/signtool-exe#see-also
https://learn.microsoft.com/en-us/dotnet/framework/whats-new/#see-also

Author: amotl

docs/admin/circuit-breaker.md

@@ -77,7 +77,7 @@ Similar exceptions exist for the other breaker types `[request]`, `[parent]`, `[
 If you experience a `CircuitBreakingException [parent]` it is because other queries/tasks were running simultaneously and their summed estimate
 exceeded `indices.breaker.total.limit`.
 
-## Further Reading
+## See also
 
 [The Circuit Breaker Mechanism in CrateDB]
 

docs/connect/index.md

@@ -132,7 +132,7 @@ bulk operations and BLOBs, which are not supported by the PostgreSQL
 protocol.
 :::
 
-:::{rubric} Further reading
+:::{rubric} See also
 :::
 
 :::::{grid}

docs/connect/java.md

@@ -185,7 +185,7 @@ Demonstrates a basic example using both the vanilla PostgreSQL JDBC Driver
 and the CrateDB JDBC Driver.
 :::
 
-## Further reading
+## See also
 
 For testing Java applications against CrateDB, see also documentation
 about {ref}`java-junit` and {ref}`testcontainers`.

docs/start/modelling/fulltext.md

@@ -145,7 +145,7 @@ WHERE
 This blend lets you query by text relevance, numeric filters, and spatial
 constraints, all in one.
 
-## Further Learning & Resources
+## See also
 
 * {ref}`Full-text Search <fulltext-search>`: In-depth
   walkthrough of full-text search capabilities.

docs/start/modelling/geospatial.md

@@ -82,7 +82,7 @@ in queries.
 
 See {ref}`Geo Search <crate-reference:sql_dql_geo_search>` for details.
 
-## Further Learning & Resources
+## See also
 
 * Reference manual:
   * {ref}`Geo Search <crate-reference:sql_dql_geo_search>`

docs/start/modelling/json.md

@@ -168,7 +168,7 @@ table is 1000, more could impact performance.
 Object fields are treated as any other column, therefore **`GROUP BY`**,
 **`HAVING`**, and **window functions** are supported.
 
-## Further Learning & Resources
+## See also
 
 * Reference Manual:
   * {ref}`Objects <crate-reference:data-types-objects>`

docs/start/modelling/relational.md

@@ -164,7 +164,7 @@ LEFT JOIN order_counts oc
     ON c.id = oc.customer_id;
 ```
 
-## Further Learning & Resources
+## See also
 
 * Reference Manual:
   * How to {ref}`query with joins <crate-reference:sql_joins>`

docs/start/modelling/timeseries.md

@@ -156,7 +156,7 @@ All types are supported within the same table or joined together.
 * Supports long‑term retention with performant historic storage.
 * Columnar layout reduces storage footprint and accelerates aggregation queries.
 
-## Further Learning & Resources
+## See also
 
 * **Documentation:** {ref}`Advanced Time Series Analysis <timeseries-analysis>`,
   {ref}`Time Series Long Term Storage <timeseries-longterm>`

docs/start/modelling/vector.md

@@ -66,7 +66,7 @@ ORDER BY _score DESC;
 This ranks results by **vector similarity** to the vector supplied by searching
 top 2 nearest neighbours.
 
-## Further Learning & Resources
+## See also
 
 * {ref}`Vector Search <vector-search>`: More details about searching with
   vectors

docs/start/query/ad-hoc.md

@@ -206,7 +206,7 @@ Learn more about how to use ad-hoc queries effectively.
 | Full-text & filter                    | Combine keyword search with structured queries                                       | {ref}`fts` <br> {ref}`crate-reference:fulltext-indices`      |
 
 
-## Further reading
+## See also
 
 :::::{grid}
 :padding: 0