Merge pull request #29 from WorldHealthOrganization/main

updating TOC

.vscode/settings.json

@@ -0,0 +1,5 @@
+{
+    "cSpell.words": [
+        "GDHCN"
+    ]
+}

README.md

@@ -6,7 +6,7 @@
 ![QA warnings](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2FWorldHealthOrganization.github.io%2Fsmart-trust%2Fqa.json&query=%24.warnings&logoColor=orange&label=QA%20warnings&color=yellow)
 ![QA hints](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2FWorldHealthOrganization.github.io%2Fsmart-trust%2Fqa.json&query=%24.hints&logoColor=yellow&label=QA%20hints&color=yellow)
 <!--/badges-->
-WHO SMART Trust
+WHO SMART Trust 
 ---
 This is the WHO SMART Trust Implementation Guide
 <br> </br>

input/pagecontent/functional.md

@@ -10,7 +10,7 @@ Consensus data models, controlled vocabularies and data transformations allow co
 *Is the vaccine credential, COVID certificate or other trusted health document verifiably from the purported issuer?​*  
 *Has the certificate remained unaltered since it was issued?​*
 
-Existing health data certificate standards use various well-defined methods of providing digital signatures in health documents based on public key crytopgraphy methods. Public key distribution within the federated registry is standardized to allow actors across networks to retrieve and process public keys, metadata, business rules, revocation data from any other actor. Universal verifier applications can use the content shared within the federated registry to extract digital signatures from health documents and verify issuer and integrity of the document content according to the specifications established by the credential standard.
+Existing health data certificate standards use various well-defined methods of providing digital signatures in health documents based on public key cryptography methods. Public key distribution within the federated registry is standardized to allow actors across networks to retrieve and process public keys, metadata, business rules, revocation data from any other actor. Universal verifier applications can use the content shared within the federated registry to extract digital signatures from health documents and verify issuer and integrity of the document content according to the specifications established by the credential standard.
 
 *Is the certificate issuer trusted by the verifier?​*
 

input/pagecontent/index.xml

@@ -11,7 +11,7 @@
 
 
   <h3>Participants</h3> <a name="participants"> </a>
-  {% include img.html img="Participant_Onboarding_Status.jpg" caption="Latest Status" width ="70%" %}
+  {% include img.html img="Participant_Onboarding_Status.jpg" caption="Latest Status" width ="70%" %}     
 
   <h3>Available Trust Domains</h3>
   {% include available_trust_domains.md %}

sushi-config.yaml

@@ -47,6 +47,24 @@ pages:
       title: Business Requirements
     concepts.md:
       title: Concepts
+      concepts_certificate_governance.md:
+        title: Concepts Certificate Governance
+      concepts_CertificatePreperation.md:
+        title: Concepts Certificate Preparation
+      concepts_did.md:
+        title: Concepts Did
+      concepts_governance.md:
+        title: Concepts Governance
+      concepts_onboarding.md:
+        title: Concepts Onboarding
+      concepts_onboarding_checklist.md:
+        title: Concepts Onboarding Checklist
+      concepts_onboarding_initialguideline_full.md:
+        title: Concepts Onboarding Initial Guidance Full
+      concepts_onboarding_initialprocess_full.md:
+        title: Concepts Onboarding Initial Process Full
+      concepts_onboarding_process_full.md:
+        title: Concepts Onboarding Process Full
     use_cases.md:
       title: Use Cases
     decision_support.md:
@@ -65,6 +83,8 @@ pages:
       title: Content profiles 
     hcert_spec.md:
       title: Electronic Health Certificate Specification
+    trust_network_gateway_architecture.md:
+      title: Trust Network Gateway Architecture
   deployment.xml:
     title: Deployment
     video_tutorial.md: