[geos-commits] [SCM] GEOS branch main updated. 80b76d6fdbd29442e5a5562f859be78807f2884a

[git at osgeo.org]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GEOS".

The branch, main has been updated
       via  80b76d6fdbd29442e5a5562f859be78807f2884a (commit)
      from  0568dc93ad05b71249f34eca683e6e958f2ee5e7 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 80b76d6fdbd29442e5a5562f859be78807f2884a
Author: Martin Davis <mtnclimb at gmail.com>
Date:   Thu May 23 20:29:32 2024 -0700

    Update DEVELOPER-NOTES.md

diff --git a/DEVELOPER-NOTES.md b/DEVELOPER-NOTES.md
index 8b47e4b1a..79f6743ca 100644
--- a/DEVELOPER-NOTES.md
+++ b/DEVELOPER-NOTES.md
@@ -5,7 +5,7 @@
   * This is just history, JTS was written first and GEOS was a slavish port.
   * Being memory managed, JTS is an easier language to prototype in.
   * Having various visual tooling, JTS is an easier platform to debug spatial algorithms in.
-  * Being Java, JTS has less language legacy than GEOS, which was originally ported when STL was still not part of the standard, and therefor reflects a mix of styles and eras.
+  * Being Java, JTS has less language legacy than GEOS, which was originally ported when STL was not part of the standard, and therefore reflects a mix of styles and eras.
 
 * Ideally, new algorithms will be implemented in JTS and then ported to GEOS.
 * Smaller performance optimizations in GEOS can travel back to JTS.

-----------------------------------------------------------------------

Summary of changes:
 DEVELOPER-NOTES.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
GEOS