Various minor docs improvements. (#608)

Author: arscan

README.md

@@ -1,10 +1,10 @@
 # ONC Certification (g)(10) Standardized API Test Kit
 
 The **ONC Certification (g)(10) Standardized API Test Kit** is a testing tool
-for Health IT systems seeking to meet the requirements of the ONC [Standardized
+for Health IT systems seeking to meet the requirements of the [Standardized
 API for Patient and Population Services criterion §
 170.315(g)(10)](https://www.healthit.gov/test-method/standardized-api-patient-and-population-services)
-in the ONC Certification Program.
+in the ONC Health IT Certification Program.
 
 The **(g)(10) Standardized API Test Kit** behaves like an API consumer, making a
 series of HTTP requests that mimic a real world client to ensure that the API
@@ -16,24 +16,28 @@ supports an approved version of each of the required standards:
   v2.0.0, or v2.2.0)
 * HL7 FHIR Bulk Data Access (Flat FHIR) (v1.0.1, or v2.0.0)
 
-Please note that US Core Implementation Guide v.7.0.0 should only be used
+_Please note that US Core Implementation Guide v.7.0.0 should only be used
 with SMART Application Launch Guide v2.0.0 or above due to granular scope
-support requirements.
+support requirements._
 
 This test kit is [open source](#license) and freely available for use or
 adoption by the health IT community including EHR vendors, health app
 developers, and testing labs. It is an approved test method for the §
-170.315(g)(10) certification criterion in the EHR Certification program by the
-Office of the National Coordinator for Health IT (ONC).
+170.315(g)(10) certification criterion in the ONC Health IT Certification
+program by the Assistant Secretary for Technology Policy (ASTP).
 
-The (g)(10) Standarized API Test Kit is built using the [Inferno
+The (g)(10) Standardized API Test Kit is built using the [Inferno
 Framework](https://inferno-framework.github.io/).  The Inferno Framework is
 designed for reuse and aims to make it easier to build test kits for any
 FHIR-based data exchange.
 
+Visit the [(g)(10) Standardized API Test Kit
+Documentation](http://github.com/onc-healthit/onc-certification-g10-test-kit/wiki)
+for information on using and contributing to this test kit.
+
 ## Getting Started
 
-ONC hosts a [public
+ASTP hosts a [public
 instance](https://inferno.healthit.gov/suites/g10_certification) of this test
 kit that developers and testers are welcome to use.  However, users are
 encouraged to download and run this tool locally to allow testing within private
@@ -42,7 +46,7 @@ Please see the [Local Installation
 Instructions](#local-installation-instructions) section below for more
 information.
 
-ONC hosts a [(g)(10) reference
+ASTP also hosts a [(g)(10) reference
 server](https://inferno.healthit.gov/reference-server/) that can be used to
 orient new users on these tests.  The [(g)(10) Standardized API Test Kit
 Walkthrough](https://github.com/onc-healthit/onc-certification-g10-test-kit/wiki/Walkthrough)

docs/README.md

@@ -2,27 +2,27 @@ The **ONC Certification (g)(10) Standardized API Test Kit** is a testing tool
 for Health IT systems seeking to meet the requirements of the ONC [Standardized
 API for Patient and Population Services criterion §
 170.315(g)(10)](https://www.healthit.gov/test-method/standardized-api-patient-and-population-services)
-in the ONC Certification Program. The following documentation provides information
+in the ONC Health IT Certification Program. The following documentation provides information
 on how to use and contribute to this test kit.
 
 ## Using this Test Kit
 
 * [Getting Started](https://github.com/onc-healthit/onc-certification-g10-test-kit/?tab=readme-ov-file#getting-started): Installation instructions for this test kit.
-* [Test Kit Walkthrough](Walkthrough): A step-by-step guide to using this test kit.
+* [Test Kit Walkthrough](Walkthrough.md): A step-by-step guide to using this test kit.
 * [Testing FAQ](FAQ.md): Frequently asked questions about the tests in this test kit.
-* [IE Browser](IE-Browser): A guide to using this test kit with legacy/unsupported versions of Internet Explorer.
+* [IE Browser](IE-Browser.md): A guide to using this test kit with legacy/unsupported versions of Internet Explorer.
 
-## Updating this Test Kit
+## Contributing to this Test Kit
 
 Developers contributing to this test kit should be familiar with [authoring
 Inferno Framework test suites](https://inferno-framework.github.io/docs/writing-tests/).  The following guides provide additional
 information about the design and implementation of this test kit to aid
 contributing to these tests:
 
-* [Technical Overview](Technical-Overview): A guide to the architecture of this test kit.
-* [Standards Update Guide](SVAP-Update-Guide): How to update this test kit when new versions of standards are approved.
-* [Terminology Update Guide](Terminology-Update-Guide): How to update terminology used in this test kit.
-* [Unusual Implementation Details](Unusual-Implementation-Details):  Gotchas and special cases to be aware of when updating this test kit.
+* [Technical Overview](Technical-Overview.md): A guide to the architecture of this test kit.
+* [SVAP Update Guide](SVAP-Update-Guide.md): How to update this test kit when new versions of standards are approved.
+* [Terminology Update Guide](Terminology-Update-Guide.md): How to update terminology used in this test kit.
+* [Unusual Implementation Details](Unusual-Implementation-Details.md): Gotchas and special cases to be aware of when updating this test kit.
 
 ## Reference Documents
 * [Test Procedure Matrix](https://github.com/onc-healthit/onc-certification-g10-test-kit/raw/refs/heads/main/onc_certification_g10_matrix.xlsx): A matrix of test procedures and their associated test cases.

docs/Technical-Overview.md

@@ -6,14 +6,14 @@ and is intended to serve multiple purposes:
   effective transfer of this software to new stewards.
 
 This document does not provide detailed instructions on how to use
-an Inferno Test Kit, the contents of the (g)(10) Certification Criteria,
+an Inferno test kit, the contents of the (g)(10) Certification Criteria,
 basics of the Inferno Framework, or details on how to use Ruby, Docker,
 or other tools.  Developers are expected to have at least a basic understanding
 of all these topics.  Please refer to the References section of this document
 for links to more information about these topics.
 
 Please note that the focus of this document are on features that are specific to
-this Test Kit and does not provide a detailed explanation of common Inferno
+this test kit and does not provide a detailed explanation of common Inferno
 Framework functionality.
 
 ## Test Design Principles and features
@@ -30,7 +30,7 @@ Tests for this test kit have been designed with the following principles:
   configuration, and tests should complete in a reasonable amount of time.
 * Limit extraneous constraints: The tests should not place additional constraints
   on the system under test.
-* Reuse existing tests when possible: Reuse tests from Test Kits that target
+* Reuse existing tests when possible: Reuse tests from test kits that target
   implementation guides that are required within this test kit.
 
 The design of the tests within this test kit reflect these principles
@@ -56,7 +56,7 @@ The (g)(10) Test Kit manages this complexity through standard software design
 practices and approaches, leveraging the functionality provided by the Ruby
 programming language.  And while this code is intended to be accessible to
 developers new to the Ruby language, developers are expected to learn the basics
-of Ruby development before attempting to alter these tests.  This Test Kit also
+of Ruby development before attempting to alter these tests.  This test kit also
 uses RSpec to "unit test" components of these tests, and developers are expected
 to learn the basics of RSpec as well.
 
@@ -67,16 +67,16 @@ FHIR Implementation Guides, while providing guidance on how to support these
 test kits to accomplish the specific requirements of the certification
 criterion.  In order to facilitate testing systems independently of the (g)(10)
 Certification requirements, each of these Implementation Guides also has a
-stand-alone Test Kit.  The (g)(10) Test Kit then imports tests defined in these
-Test Kits and integrates them into a single cohesive test procedure, while also
+stand-alone test kit.  The (g)(10) Test Kit then imports tests defined in these
+test kits and integrates them into a single cohesive test procedure, while also
 further constraining their implementation to meet any (g)(10)-specific
 requirements.
 
 *Please note that the Multi-Patient API tests do not currently reuse
 the SMART Bulk Data Test Kit.  A future version of this test kit
 may reuse the SMART Bulk Data Test Kit.*
 
-The specific Test Kits that are imported into this Test Kit include:
+The specific test kits that are imported into this test kit include:
 
 1. **[US Core Test Kit](https://github.com/inferno-framework/us-core-test-kit)**:
   Data access within the Single Patient API tests in this Test Kit are
@@ -104,7 +104,7 @@ libraries.  It is organized into several main directories:
 The (g)(10) Test Kit contains a single suite of tests, which is capable of testing
 any valid combination of approved standards for certification.  This suite
 is defined in `lib/onc_certification_g10_test_kit.rb` and imports all necessary
-tests from both external Test Kits and from within the (g)(10) Test Kit itself.
+tests from both external test kits and from within the (g)(10) Test Kit itself.
 
 ## Testing Code Changes
 
@@ -128,7 +128,7 @@ likely to change.
 
 ### End-to-End testing
 
-Besides the unit tests provided within this Test Kit, after each update
+Besides the unit tests provided within this test kit, after each update
 the tests should be validated against a complete server implementation
 that is known to be correct.  The Inferno Reference Server provides this functionality,
 and contains data that passes all of these tests.  Note that if test changes

docs/Terminology-Update-Guide.md

@@ -44,7 +44,7 @@ the version of UMLS should be updated approximately yearly to incorporate any
 new valid codes that may have been introduced.  These two updates are typically done together,
 and the following instructions assume this is the case. During this process,
 metadata about the CodeSystems and ValueSets (e.g. number of codes in each) is
-also updated and stored within the Test Kit.  This enables the (g)(10) Test Kit
+also updated and stored within the test kit.  This enables the (g)(10) Test Kit
 to provide a warning to users if they need to rerun the terminology update
 process.
 

docs/Unusual-Implementation-Details.md

@@ -1,5 +1,5 @@
 
-While code in this Test Kit is intended to be as simple and as
+While code in this test kit is intended to be as simple and as
 easy-to-understand as possible, sometimes unanticipated testing requirements are
 introduced that require special handling.  The ability for Inferno to
 accommodate these requirements is a key feature of the Inferno framework.

docs/Walkthrough.md

@@ -7,17 +7,17 @@ criterion](https://www.healthit.gov/test-method/standardized-api-patient-and-pop
 of the [21st Century Cures Act: Interoperability, Information Blocking, and the
 ONC Health IT Certification
 Program](https://www.govinfo.gov/content/pkg/FR-2019-03-04/pdf/2019-02224.pdf).
-It uses the [ONC-hosted
+It uses the [ASTP-hosted
 instance](https://inferno.healthit.gov/suites/g10_certification) of the (g)(10)
 Standardized API Test Kit to test against a [publicly available reference
 server](https://inferno.healthit.gov/reference-server) that mimics a (g)(10)
 conformant API.
 
 At the end of this walkthrough, you will be able to use the **Inferno ONC
 Certification (g)(10) Standardized API Test Kit** to evaluate APIs for
-conformance to the ONC (g)(10) certification criteria. If you are interested in
+conformance to the ONC (g)(10) certification criterion. If you are interested in
 how to use the Inferno Framework to test other FHIR-based data exchanges that
-fall outside the scope of ONC (g)(10) certification criteria, please visit the
+fall outside the scope of ONC (g)(10) certification criterion, please visit the
 [Inferno Framework](https://inferno-framework.github.io) for more information.
 
 * [Step 1: Create a new (g)(10) Test Session](#step-1-create-a-new-inferno-g10-test-session-and-select-standard-versions)
@@ -40,7 +40,7 @@ fall outside the scope of ONC (g)(10) certification criteria, please visit the
 * Go to <https://inferno.healthit.gov>.
 * Select 'ONC (g)(10) Standardized Test Kit' under 'ONC Health Certification
   Program', which is an instance of Inferno configured to specifically test
-  the requirements of the criteria in the ONC Health IT Certification Program.
+  the requirements of the criterion in the ONC Health IT Certification Program.
 
 ![step-01-landing](images/step-01-landing.png)
 
@@ -83,7 +83,7 @@ pane, or click 'Standalone Patient App' in the menu on the left.
 
 ## Step 3: Perform Standalone Patient App Tests
 
-Inferno's tests for the ONC certification criteria are organized into seven steps.
+Inferno's tests for the ONC certification criterion are organized into seven steps.
 This allows the tester to walk through the requirements in an order similar to
 what would be done in a real-world situation, while limiting redundant testing.
 

docs/_Footer.md

@@ -1,3 +1,5 @@
-_Test Kit documentation is stored within the `/docs` folder of this git repository
-and is automatically copied to the wiki with each update to the `main` branch.
-Do not change content within the wiki directly as changes will be overwritten._
+_Test kit documentation is stored within the [./docs](../tree/main/docs) folder of
+this repository and is automatically synchronized to this wiki with each update
+to the `main` branch using the [Publish Docs Wiki
+workflow](../actions/workflows/publish-docs-wiki.yml).  Do not change content
+within this wiki directly as changes will be overwritten._

docs/_Sidebar.md

@@ -6,7 +6,7 @@
   - [Testing FAQ](FAQ)
   - [IE Browser Notes](IE-Browser)
 
-**Updating this Test Kit**
+**Contributing to this Test Kit**
   - [Technical Overview](Technical-Overview)
   - [Standards Update Guide](SVAP-Update-Guide)
   - [Terminology Update Guide](Terminology-Update-Guide)