Some minor linguistic and markdown-syntactic corrections

busstoptaktik · Aug 17, 2023 · ee9b418 · ee9b418
1 parent 8032925
commit ee9b418
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 6 deletions.
diff --git a/ruminations/000-rumination.md b/ruminations/000-rumination.md
@@ -236,7 +236,7 @@ ctx.apply(ed50_wgs84, Fwd, data);
 Then a user defined operator:
 
 ```rust
-use geodesy::operator_authoring::*;
+use geodesy::authoring::*;
 
 // See examples/03-user-defined-operators.rs for implementation details
 pub struct MyNewOperator {

diff --git a/ruminations/003-rumination.md b/ruminations/003-rumination.md
@@ -154,12 +154,11 @@ On the occasion of Knud Poder's 90th birthday in 2015, I wrote a few words about
 > /Thomas Knudsen, Danish Geodata Agency
 >
 >
-> [1] Thomas Knudsen, Simon L. Kokkendorff, Karsten E. Engsager (2012): A Vivid Relic Under Rapid Transformation, OSGeo Journal vol. 10, pp. 55-57, URL https://journal.osgeo.org/index.php/journal/article/download/200/167
+> [1] Thomas Knudsen, Simon L. Kokkendorff, Karsten E. Engsager (2012): A Vivid Relic Under Rapid Transformation, OSGeo Journal vol. 10, pp. 55-57, URL <https://journal.osgeo.org/index.php/journal/article/download/200/167>
 >
 > [2] R. König and K. H. Weise (1951): Mathematische Grundlagen der Höheren Geodäsie und Kartographie, Erster Band. Springer, Berlin/Göttingen/Heidelberg, 1951.
 >
-> [3] L. Krüger (1912): Konforme Abbildung des Erdellipsoids in der Ebene. Neue Folge 52. Royal Prussian Geodetic Institute, Potsdam. URL http://bib.gfz-potsdam.de/pub/digi/krueger2.pdf
-
+> [3] L. Krüger (1912): Konforme Abbildung des Erdellipsoids in der Ebene. Neue Folge 52. Royal Prussian Geodetic Institute, Potsdam. URL <http://bib.gfz-potsdam.de/pub/digi/krueger2.pdf>
 
 ### Document History
 

diff --git a/ruminations/004-rumination.md b/ruminations/004-rumination.md
@@ -70,7 +70,7 @@ In a sense, this reflects the modularity of the transformation operator implemen
 
 ### Problem #3: The geodetic registry interface ("the resolver")
 
-In PROJ, much automation effort is spent trying to guess the most appropriate transformation betwwen any two CRS. Let's call this effort "resolving" and the contraption implementing that "the resolver".
+In PROJ, much automation effort is spent trying to guess the most appropriate transformation between any two CRS. Let's call this effort "resolving" and the contraption implementing that "the resolver".
 
 PROJ is built on the idea that the users should know what system (e.g. represented as an EPSG CRS code) their data are comming from, and which system they want them transformed to. RG on the other hand is built on the much simpler idea, that the users should know which transformation they want to apply.
 

diff --git a/ruminations/005-rumination.md b/ruminations/005-rumination.md
@@ -39,7 +39,7 @@ With that noted, here comes the abstract
 
 ---
 
-### Divided by a common language: Bridging the gap between the ideal world of geoinformatics and the messy realities of geodesy.
+### Divided by a common language: Bridging the gap between the ideal world of geoinformatics and the messy realities of geodesy
 
 **Geodetic terminology** has always been messy - for instance, geodesists in general do not care whether point identification is given as geographic, geocentric or projected coordinates, as long as it makes geodetic sense, i.e. as long as the reference frame in use allows lossless conversion between those coordinates.
-Original file line number
+Diff line change
@@ Expand Up / @@ -39,7 +39,7 @@ With that noted, here comes the abstract @@
     ---
-    ### Divided by a common language: Bridging the gap between the ideal world of geoinformatics and the messy realities of geodesy.
+    ### Divided by a common language: Bridging the gap between the ideal world of geoinformatics and the messy realities of geodesy
     **Geodetic terminology** has always been messy - for instance, geodesists in general do not care whether point identification is given as geographic, geocentric or projected coordinates, as long as it makes geodetic sense, i.e. as long as the reference frame in use allows lossless conversion between those coordinates.
@@ Expand Down @@