Following some rabbit suggestions

Author: cvvergara

NEWS.md

@@ -16,26 +16,26 @@ milestone for 3.8.0
 **Promotion to official function of pgRouting.**
 
 * [#2772](https://github.com/pgRouting/pgrouting/issues/2772):
-  Promote to official pgr_extractVertices in 3.8
+  Promoted to official pgr_extractVertices in version 3.8
 
   * Error messages adjustment.
   * Function promoted to official.
 
 * [#2760](https://github.com/pgRouting/pgrouting/issues/2760):
-  Promote to official pgr_degree in 3.8
+  Promoted to official pgr_degree in version 3.8
 
   * Error messages adjustment.
   * New signature with only Edges SQL.
   * Function promoted to official.
 
 * [#2774](https://github.com/pgRouting/pgrouting/issues/2774):
-  Promote to official pgr_findCloseEdges in 3.8
+  Promoted to official pgr_findCloseEdges in version 3.8
 
   * Error messages adjustment.
   * ``partial`` option is removed.
   * Function promoted to official.
 
-**New proposed functions**
+**Proposed functions**
 
 * Contraction
 
@@ -72,7 +72,7 @@ milestone for 3.8.0
 * [#2850](https://github.com/pgRouting/pgrouting/issues/2850):
   Rewrite pgr_nodeNetwork
 
-**Deprecation of functions.**
+**Deprecation of SQL functions**
 
 * [#2749](https://github.com/pgRouting/pgrouting/issues/2749):
   Deprecate pgr_AlphaShape in 3.8
@@ -85,10 +85,10 @@ milestone for 3.8.0
 * [#2826](https://github.com/pgRouting/pgrouting/issues/2826):
   Deprecate pgr_createVerticesTable in 3.8
 
-Deprecated functions:
+In the deprecated functions:
 
 - Migration section is created.
-- The use removed.
+- The use of the functions is removed in the documentation.
 
 ## pgRouting 3.7
 

doc/categories/withPoints-category.rst

@@ -264,7 +264,7 @@ for this example:
 Driving side
 ...............................................................................
 
-In the the following images:
+In the following images:
 
 - The squared vertices are the temporary vertices,
 - The temporary vertices are added according to the driving side,

doc/conf.py.in

@@ -332,6 +332,7 @@ linkcheck_ignore = [
     #        (see: https://github.com/sphinx-doc/sphinx/issues/7388)
     r'https://github.com/pgRouting/pgrouting/issues/*',    # limit only pgrouting
     r'https://github.com/pgRouting/pgrouting/archive/*',
+    r'https://docs.pgrouting.org/3.8/*',
     r'https://www.overpass-api.de/*'
 ]
 

doc/src/release_notes.rst

@@ -46,27 +46,27 @@ milestone for 3.8.0
 .. rubric:: Promotion to official function of pgRouting.
 
 * `#2772 <https://github.com/pgRouting/pgrouting/issues/2772>`__:
-  Promote to official pgr_extractVertices in 3.8
+  Promoted to official pgr_extractVertices in version 3.8
 
   .. include:: pgr_extractVertices.rst
      :start-after: Version 3.8.0
      :end-before: .. rubric
 
 * `#2760 <https://github.com/pgRouting/pgrouting/issues/2760>`__:
-  Promote to official pgr_degree in 3.8
+  Promoted to official pgr_degree in version 3.8
 
   .. include:: pgr_degree.rst
      :start-after: Version 3.8.0
      :end-before: .. rubric
 
 * `#2774 <https://github.com/pgRouting/pgrouting/issues/2774>`__:
-  Promote to official pgr_findCloseEdges in 3.8
+  Promoted to official pgr_findCloseEdges in version 3.8
 
   .. include:: pgr_findCloseEdges.rst
      :start-after: Version 3.8.0
      :end-before: .. rubric
 
-.. rubric:: New proposed functions
+.. rubric:: Proposed functions
 
 * Contraction
 
@@ -101,7 +101,7 @@ milestone for 3.8.0
 * `#2850 <https://github.com/pgRouting/pgrouting/issues/2850>`__:
   Rewrite pgr_nodeNetwork
 
-.. rubric:: Deprecation of functions.
+.. rubric:: Deprecation of SQL functions
 
 * `#2749 <https://github.com/pgRouting/pgrouting/issues/2749>`__:
   Deprecate pgr_AlphaShape in 3.8
@@ -114,10 +114,10 @@ milestone for 3.8.0
 * `#2826 <https://github.com/pgRouting/pgrouting/issues/2826>`__:
   Deprecate pgr_createVerticesTable in 3.8
 
-Deprecated functions:
+In the deprecated functions:
 
 - Migration section is created.
-- The use removed.
+- The use of the functions is removed in the documentation.
 
 pgRouting 3.7
 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

doc/tsp/pgr_TSP.rst

@@ -67,18 +67,18 @@ Description
 
     - When ``start_vid = 0 OR end_vid = 0``
 
-      - The solutions generated is guaranteed to be *twice as long as the
+      - The solutions generated are guaranteed to be *twice as long as the
         optimal tour in the worst case*
 
     - When ``start_vid != 0 AND end_vid != 0 AND start_vid != end_vid``
 
-      - It is **not guaranteed** that the solution will be, in the worse case,
+      - It is **not guaranteed** that the solution will be, in the worst case,
         twice as long as the optimal tour, due to the fact that `end_vid` is
         forced to be in a fixed position.
 
   - With ``directed => true``
 
-    - It is **not guaranteed** that the solution will be, in the worse case,
+    - It is **not guaranteed** that the solution will be, in the worst case,
       twice as long as the optimal tour
     - Will generate a graph that:
 

doc/tsp/pgr_TSPeuclidean.rst

@@ -52,7 +52,7 @@ Description
    :start-after: tsp characteristics start
    :end-before: tsp characteristics end
 
-- Any duplicated identifier will be ignored. The coordinates than will be kept
+- Any duplicated identifier will be ignored. The coordinates that will be kept
   is arbitrarily.
 
   - The coordinates are quite similar for the same identifier, for example