0.190.0

README.md

@@ -39,9 +39,9 @@ See [rush.json](./rush.json) for the list of packages. These packages are descri
 * `test-apps/display-test-app/package.json`
   * Private, not published
   * Test application for graphics visualization
-* `test-apps/testbed/package.json`
+* `integration-tests/core/package.json`
   * Private, not published
-  * Test application for frontend/backend interaction
+  * Integration tests for frontend/backend interaction using standard RPC interfaces
 
 Each package will have its own **node_modules** directory which will contain symbolic links to *common* dependencies managed by Rush.
 
@@ -88,7 +88,7 @@ Note that it is a good idea to `rush install` after each `git pull` as dependenc
 3. Locally commit changes: `git commit` (or use the Visual Studio Code user interface)
 4. Repeat steps 1-3 until ready to push changes
 5. Add changelog entry (which could potentially cover several commits): `rush change`
-6. Follow prompts to enter a change description or press ENTER if the change does not warrant a changelog entry. If multiple packages have changed, multiple sets of prompts will be presented. If the changes are only to non-published packages (like **testbed**), then `rush change` will indicate that a changelog entry is not needed.
+6. Follow prompts to enter a change description or press ENTER if the change does not warrant a changelog entry. If multiple packages have changed, multiple sets of prompts will be presented. If the changes are only to non-published packages (like **display-test-app**), then `rush change` will indicate that a changelog entry is not needed.
 7. Completing the `rush change` prompts will cause new changelog entry JSON files to be created.
 8. Check for API signature changes: `rush extract-api`.  This will update the signature files, located in `common/api`.
 9. Review any diffs to the API signature files in the `common/api` directory to ensure they are compatible with the intended release of the package