Merge pull request #8 from DTLab-LabCN/regis-wip-local

More minor edits.

docs/dtt_overview/_category_.json

@@ -3,6 +3,6 @@
   "position": 1,
   "link": {
     "type": "generated-index",
-    "description": "DTLab's Digital Trust Testbench (DTT) Overview"
+    "description": "DTT is a cloud-based, quality assurance tool for digital credential solutions."
   }
 }

docs/dtt_overview/dtt_how_can_i_contribute.md

@@ -4,4 +4,6 @@ sidebar_position: 3
 
 # How can I contribute to DTT?
 
-[Contact us!](mailto:[email protected])
+We work on a variety of projects in the digital credential space that require different skill sets and expertise. We look to collaborators to contribute to DTLab projects, to ensure we have the right breadth and depth when we need it. Collaborators may be DTLab any government, organization, or individual. DTLab welcomes everyone in collaborating with us on a project.
+
+If you are interested in trying out DTT, have feedback, or suggestions for us, please [Contact us!](mailto:[email protected])

docs/dtt_overview/dtt_what_is_dtt.md

@@ -5,8 +5,10 @@ sidebar_position: 1
 
 # What is DTT?
 
-![DTT Workshop](../images/dtt-workshop.png)
+![DTT is a cloud-based, quality assurance tool for digital credential solutions](../images/dtt-workshop.png)
 
-**Digital Trust Test Bench (DTT)** is a quality assurance tool for digital credential solutions, allowing governments and organizations to put digital credentials to the test to make sure they work with other platforms.
+**Digital Trust Test Bench (DTT)** is a cloud-based, quality assurance tool for digital credential solutions. It provides  turnkey tools for digital credential industry players and government partners to test out their technology and confirm it works with one another. This testing is a key component to scaling digital credentials across the country (and the world) with the goal of making them ubiquitous.
 
 DTT is not: a certification or compliance tool.
+
+For more information, check out [https://dtlab-labcn.org/en/digital-trust-test-bench/](https://dtlab-labcn.org/en/digital-trust-test-bench/) or [Contact us](mailto:[email protected]).

docs/dtt_overview/dtt_who_develops_and_maintain.md

@@ -4,6 +4,9 @@ sidebar_position: 2
 
 # Who develops and maintains DTT?
 
-**_TO-DO_**: reuse existing content!
+DTLab and its technical partners develop, host, and maintain DTT.
 
-Note: standards are evolving, those test suites are designed to quickly adapt to those needs.
+**_Note_**: DTLab was awarded a 12-month (2024/2025) testing stream contract to test its Digital Trust Test Bench (DTT) with Shared Services Canada and Canadian Digital Service. The contract follows DTLab’s qualification under [Innovative Solutions Canada’s](https://ised-isde.canada.ca/site/innovative-solutions-canada/) (ISC) “Digitization and Cybersecurity” call for prototypes of platforms.
+
+The program is designed to provide testing and government feedback to organizations that are preparing innovations to go to market. DTLab qualified under the ISC outcome focused on digital credential testing for technical conformity and/or compatibility.
+See our _DTLab begins testing its Digital Trust Test Bench with federal government partners_ [announcenemt](https://dtlab-labcn.org/en/dtlab-begins-testing-its-digital-trust-test-bench-with-federal-government-partners/).

docs/mdl_testing/mdl_testing_intro.md

@@ -2,6 +2,6 @@
 sidebar_position: 1
 ---
 
-# Introduction to API endpoint testing with DTT {#introduction-to-api-endpoint-testing-with-dtt}
+# Introduction to mDL testing with DTT {#introduction-to-mdl-testing-with-dtt}
 
-**_TODO_**: Focus on core VC capabilities: issue, verify, revoke. The objective is to help understand the interop capabilities of a specific endpoint by analyzing the interactions between this test suite and that endpoint.
+**_TODO_**: Focus on 18013-5 and mDL retrieval via BLE device engagement between web app and mobile device.

docs/w3c_did/did_about.md

@@ -15,9 +15,7 @@ More information on the godiddy resolver service can be found [here](https://doc
 
 * Learn more about DIDs:
   * [W3C DID Core Recommendation 1.0](https://www.w3.org/TR/did-core/)
-  * [W3C DID Core Editor's Draft 1.1](https://w3c.github.io/did-core/)
-
+
 * Get involved:
-
   * [W3C DID Working Group](https://www.w3.org/2019/did-wg/)
   * [DIF Identifiers & Discovery Working Group](https://github.com/decentralized-identity/identifiers-discovery/)

docs/w3c_did/did_how_to_use.md

@@ -13,6 +13,6 @@ To get started, enter the URL representing a DID, and click on **Resolve DID**.
 [https://dev.uniresolver.io/](https://dev.uniresolver.io/) and [https://godiddy.com/app/resolve](https://godiddy.com/app/resolve) provide a number of examples for a variety of DID methods.
 Here are a few to get you started!
 
-- did:cheqd:testnet:55dbc8bf-fba3-4117-855c-1e0dc1d3bb47
-- did:ebsi:zkC6cUFUs3FiRp2xedNwih2
-- did:indy:indicio:demo:KKyAeG7woJMV6MhhAREVKp
+>`did:cheqd:testnet:55dbc8bf-fba3-4117-855c-1e0dc1d3bb47`
+> `did:ebsi:zkC6cUFUs3FiRp2xedNwih2`
+> `did:indy:indicio:demo:KKyAeG7woJMV6MhhAREVKp`

docs/w3c_vcdm/vcdm_about.md

@@ -11,5 +11,5 @@ sidebar_position: 6
 * Learn more about the W3C Verifiable Credential Data Model:
   * Verifiable Credentials Data Model v1.1 - [W3C Recommendation](https://www.w3.org/TR/vc-data-model/)
   * Verifiable Credentials Data Model v2.0 - [W3C Candidate Recommendation Draft](https://www.w3.org/TR/vc-data-model-2.0/)
-
+  
 * Get involved: [Verifiable Credentials Working Group](https://www.w3.org/2017/vc/WG/)