(no commit message)

diff --git a/design/revisedclientarchitecture.mdwn b/design/revisedclientarchitecture.mdwn
index c8e8848..17dfefc 100644 (file)
--- a/design/revisedclientarchitecture.mdwn
+++ b/design/revisedclientarchitecture.mdwn
@@ -42,7 +42,7 @@ The re-factored Moonshot Client software will have the following components:
   * one version for web storage, restful API. (Not in scope for this iteration).
   * other versions as required for different storage solutions  (Not in scope for this iteration).
 
-*_identity-provisioning_* - not implemented in the first iteration. Provides CRUD operations via (for now) .msht and XML files, and via command line. Implemented in portable code as far as possible. Uses *_identity-server_*. Consists of
+*_identity-provisioning_* - not implemented in the initial implementation. Provides CRUD operations via (for now) .msht and XML files, and via command line. Implemented in portable code as far as possible. Uses *_identity-server_*. Consists of
 
 - *_identity-provisioning-file-handler_* - processes .msht (and, in future iterations, XML and/or json, and maybe other format) files for file-based provisioning operations. Currently implemented as *_moonshot-webp_*, allowing only install access. In future iterations it will also allow uninstall/revoke access.
 - *_identity-provisioning-cli-handler_* - provides a command line API to identity CRUD functions
@@ -83,7 +83,7 @@ The *_identity-provisioning-cli-handler_* component is not part of the current i
 
 ### Use Case Implementation
 
-The re-factored software is designed to implement the following use cases that were part of the first iteration:
+The re-factored software is designed to implement the following use cases that were part of the initial implementation:
 
 1. User installs and identity by clicking on a .msht file downloaded from the Web
 1. User creates and installs an identity card using the UI