diff --git a/docs/1054-operational-guide.asciidoc b/docs/1054-operational-guide.asciidoc
index aef8913..67e7a50 100644
--- a/docs/1054-operational-guide.asciidoc
+++ b/docs/1054-operational-guide.asciidoc
@@ -378,7 +378,7 @@ tool, that fully supports the encoding requirements defined in
 xref:1047-metadata-guidelines-for-geospatial-data-resources-part-3#ref28[28]
 and uses the UK Location XSD and Schematron schemas
 xref:1047-metadata-guidelines-for-geospatial-data-resources-part-3#ref28[28],xref:1047-metadata-guidelines-for-geospatial-data-resources-part-3#ref30[30],
-to ensure that your metadata is fully compliant with UKL and INSPIRE
+to ensure that your metadata is fully compliant with UK Location and INSPIRE
 requirements.*
 
 GEMINI 2.3 metadata is encoded in XML, as described in
@@ -448,6 +448,17 @@ e.g.service=WMS&request=GetCapabilities&, or the location of
 further information about a service.
 |===
 
+==== 3.1.4 Validation against Gemini 2.3
+
+When harvesting Gemini 2.3 records to the DMS it is important that the correct configuration
+is used in the harvest settings. Specifically, in the *harvest Configuration* settings, the following
+json must be included:
+
+[source,json]
+----
+{"validator_profiles": ["iso19139eden", "constraints-1.4", "gemini2-3"]}
+----
+
 === 3.2 Data Provider Licence information
 [#DataProvider_Licence]
 
diff --git a/docs/partials/coupledresource.asciidoc b/docs/partials/coupledresource.asciidoc
index bfd6ae7..be42094 100644
--- a/docs/partials/coupledresource.asciidoc
+++ b/docs/partials/coupledresource.asciidoc
@@ -31,7 +31,7 @@ This may be:
 
 |Examples |http://image2000.jrc.ec.europa.eu/#image2000_1_n12_multi
 
-|Revision date |December 2025
+|Revision date |February 2026
 |===
 
 .Corresponding element in other standards...
diff --git a/docs/snippets/coupledresource-waf.xml b/docs/snippets/coupledresource-waf.xml
index 785b953..412e2c2 100644
--- a/docs/snippets/coupledresource-waf.xml
+++ b/docs/snippets/coupledresource-waf.xml
@@ -3,7 +3,7 @@
   <gmd:identificationInfo>
     <srv:SV_ServiceIdentification>
       ...
-      <srv:operatesOn xlink:href='http://mywaf.com/metadata/dataset.xml'/>
+      <srv:operatesOn xlink:href='http://mywaf.com/metadata/dataset.xml#id=file-uuid'/>
     </srv:SV_ServiceIdentification>
   </gmd:identificationInfo>
   ...