update with link to demo

glossary.md

@@ -11,8 +11,7 @@
 
 **Client**: Software that runs on an asset owner's device and initiates workflows involving secrets.
 
-**Demo repository**: A repository that demonstrates usage of the client and server libraries. <br>
-- [TODO #93](https://github.com/boltlabs-inc/key-mgmt/issues/93): Add location after set-up.
+**Demo repository**: A [repository](https://github.com/boltlabs-inc/key-mgmt-demo) that demonstrates usage of the client and server libraries.
 
 **Endpoint**: A gRPC method that establishes a session and determines which protocol or workflow will be executed within that session.
 

repository-list.md

@@ -6,10 +6,9 @@ Our libraries exist in the [`key-mgmt`](https://github.com/boltlabs-inc/key-mgmt
 - [`key-server`](https://github.com/boltlabs-inc/key-mgmt/tree/develop/dams-key-server): This binary can be integrated into a host server in order to provide end-to-end encrypted storage of secrets. See [here](systems-architecture.md#key-server) for more details.
 
 ## Demo Repository
-We will add a link to a repository that demonstrates usage of the `client` and `key-server` libraries.<br>
-- [TODO #93](https://github.com/boltlabs-inc/key-mgmt/issues/93) Add link to location above.
+We have created a [demo repository](https://github.com/boltlabs-inc/key-mgmt-demo) that demonstrates usage of the `client` and `key-server` libraries.
 
-This demo contains two parts:
+This demo contains three parts:
 1. A sample human-facing calling application that integrates the `client` library. That is, this application provides an interface between the asset owner and the key-mgmt `client` API.
 1. A demonstration setup for the key server.
-1. A Dockerfile for testing the sample calling app with the `client` library and key server on any machine.
+1. In the future, will include a Dockerfile for testing the sample calling app with the `client` library and key server on any machine.