Merge pull request #1286 from georust/mkirk/cascaded_union-fixups

fixup unary_union docs
georust · Dec 19, 2024 · 0182a60 · 0182a60
2 parents d28970f + b74a708
commit 0182a60
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
@@ -26,6 +26,7 @@ jobs:
       - geo_postgis
       - geo_fuzz
       - bench
+      - docs
     if: success()
     steps:
       - name: Mark the job as a success

diff --git a/geo/src/algorithm/bool_ops/mod.rs b/geo/src/algorithm/bool_ops/mod.rs
@@ -39,7 +39,7 @@ use i_overlay::string::clip::ClipRule;
 ///
 /// # Performance
 ///
-/// For union operations on a large number of [`Polygon`]s or [`MultiPolygons`],
+/// For union operations on a large number of [`Polygon`]s or [`MultiPolygon`]s,
 /// using [`unary_union`] will yield far better performance.
 pub trait BooleanOps {
     type Scalar: BoolOpsNum;
@@ -129,7 +129,7 @@ pub enum OpType {
 /// This is typically much faster than `union`ing a bunch of geometries together one at a time.
 ///
 /// Note: Geometries can be wound in either direction, but the winding order must be consistent,
-/// and the polygon's interiors must be wound opposite to its exterior.
+/// and each polygon's interior rings must be wound opposite to its exterior.
 ///
 /// See [Orient] for more information.
 ///