From a7804b713242abfb42659687c2981ddc7cf59187 Mon Sep 17 00:00:00 2001
From: Simon Cox <dr.shorthair@pm.me>
Date: Sun, 30 Aug 2026 17:15:00 +1000
Subject: [PATCH] Minor clarifications - plan pattern

---
 ssn/chapters/ModelPlan.html | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/ssn/chapters/ModelPlan.html b/ssn/chapters/ModelPlan.html
index 9f66bcdc..d58eabd9 100644
--- a/ssn/chapters/ModelPlan.html
+++ b/ssn/chapters/ModelPlan.html
@@ -4,7 +4,7 @@ <h3>Planning executions and collections</h3>
     Sampling) at some future time.
     Collections of Samples or Executions can be described ahead of their completion, to indicate the intention
     to make collections with the given properties at a future date.
-    Here we describe patterns that may be used in this way.
+    Patterns that may be used in this way are described here.
 </p>
 
 <section id="ModelPlan-Deployment">
@@ -44,7 +44,8 @@ <h4>Planned Collection using generic system</h4>
     <p>
         More generically, a Collection (i.e., <a>sosa:ActuationCollection</a>, <a>sosa:ObservationCollection</a>,
         <a>sosa:SamplingCollection</a>, or <a>sosa:SampleCollection</a>) can be described which is made by a potential
-        deployment, where the actual system is only specified in terms of the Procedure implemented.
+        deployment. 
+        In this case the actual system is only specified in terms of the Procedure implemented.
     </p>
     <p>
         For example, <a href="#Fig-PlannedSampleCollection"></a> describes a potential set of samples (`ex:SC-LaJ2`) of
@@ -70,10 +71,11 @@ <h4>Planned Collection using generic system</h4>
         (`ex:ObsColpH`),
         packaged in a <a>sosa:ObservationCollection</a>, whose (proximate) feature of interest is the set of Samples
         described above (`ex:SC-LaJ2`).
-        Each member of the <a>sosa:ObservationCollection</a>must be consistent with the
-        <a href="#SOSAObservationCollection">requirements for membership of an ObservationCollection</a> - i.e., be
-        sampled on the specified <a>sosa:Platform</a> using the nominated <a>sosa:ObservingProcedure</a> (`ex:pH-A56`),
-        and whose <a>sosa:hasFeatureOfInterest</a> must be a member of the set of Samples (`ex:SC-LaJ2`).
+        Each member of the <a>sosa:ObservationCollection</a> must be consistent with the
+        <a href="#SOSAObservationCollection">requirements for membership of an ObservationCollection</a>.  
+        It must use the nominated <a>sosa:ObservingProcedure</a> (`ex:pH-A56`),
+        and its <a>sosa:hasFeatureOfInterest</a> must be a member of the set of Samples (`ex:SC-LaJ2`), 
+        from the same Platform (`ex:LOIRE_A_JARGEAU_WQ_Station`).
         Again, the actual System (<a>sosa:Sensor</a>) is not specified, only that it must implement the nominated
         ObservingProcedure.
     </p>