diff --git a/guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/Identifier-Guidance/Index.page.md b/guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/Identifier-Guidance/Index.page.md
index caaadd11..6395e283 100644
--- a/guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/Identifier-Guidance/Index.page.md
+++ b/guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/Identifier-Guidance/Index.page.md
@@ -1,6 +1,6 @@
 # {{page-title}}
 
-<div id="newAsset" markdown="span" class="alert alert-success" role="alert"><h4><i class="fa fa-star">
+<div id="newAsset" markdown="span" class="alert alert-success" role="alert"><h4><i class="fa fa-star"></i></h4>
 <h2> Principles</h2>
 The following principles apply to the definition and use of identifier systems within UK Core–conformant implementations:
 
@@ -19,15 +19,15 @@ Implementations SHOULD NOT assume system URIs are permanently resolvable or immu
 
 
 - Use of the NamingSystem resource is OPTIONAL.
-NamingSystem resources are intended for historical reference and documentation only. Implementations SHOULD NOT rely on the presence of a NamingSystem for runtime processing or validation.
+NamingSystem resources are intended for historical reference and documentation only. 
 
 
 - Do not rely on assigner or type for processing or search.
 Best practice is to avoid dependence on Identifier.assigner or Identifier.type, as neither element is reliably searchable across implementations.
 
-See <a href="https://build.fhir.org/datatypes.html#Identifier">DataTypes - Identifier</a> and <a hred="https://build.fhir.org/ig/HL7/fhir-for-fair/FHIRidentifiers.html>FHIR for FAIR - FHIR Identifiers</a>for more information
+See <a href="https://build.fhir.org/datatypes.html#Identifier">DataTypes - Identifier</a> and <a href="https://build.fhir.org/ig/HL7/fhir-for-fair/FHIRidentifiers.html">FHIR for FAIR - FHIR Identifiers</a>for more information
 
-<h2>Identifier System Preferred Approach</h2>
+<h2>Identifier System Example Approach</h2>
 
 Where a recognised identifier system exists, or one can reasonably be established:
 
diff --git a/guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/toc.yaml b/guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/toc.yaml
index e0860b11..5159f080 100644
--- a/guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/toc.yaml
+++ b/guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/toc.yaml
@@ -1,5 +1,7 @@
 - name: Sitemap Overview
   filename: Sitemap-Overview
+- name: Identifier Guidance
+  filename: Identifier-Guidance
 - name: DataType Guidance
   filename: DataTypeGuidance
 - name: CodeableConcept Guidance
@@ -10,5 +12,4 @@
   filename: MustSupport-Guidance
 - name: Lifecycle
   filename: Lifecycle
-- name: Identifier Guidance
-  filename: Identifier-Guidance
+
diff --git a/guides/UKCoreVersionHistory/Home/STU3-Sequence.page.md b/guides/UKCoreVersionHistory/Home/STU3-Sequence.page.md
index 41d50001..3ffddee9 100644
--- a/guides/UKCoreVersionHistory/Home/STU3-Sequence.page.md
+++ b/guides/UKCoreVersionHistory/Home/STU3-Sequence.page.md
@@ -22,6 +22,7 @@ topic: STU3Sequence
 <br>
 <b>General IG improvements:</b><br>
 <ul>
+<li>Added guidance on use of SNOMED CT UK Edition to Terminology Index page
 <li>Changed all VitalSigns derived profiles baseDefinitions to reference HL7 Internal profiles. This ensures international conformance as per <a href="https://build.fhir.org/observation.html#core">10.1.1.1 Core Profiles for Observation</a>.
 <li>Removed IG pages and references to retired and deleted R5 backport Extensions.</li>
 <li>Removed references to retired and deleted R5 backport Extensions in StructureDefinition assets: <code>UKCore-DiagnosticReport-Lab</code>; <code>UKCore-DiagnosticReport</code>; <code>UKCore-FamilyMemberHistory</code>; <code>UKCore-Observation-Lab</code>; <code>UKCore-Observation</code>; and <code>UKCore-Specimen</code>.</li>