message: Update swagger-accuracy-report.md
diff: -# Swagger Accuracy Report
  -## What is this report about
  -[@Jeffrey to add details]
  +# Service Contract Accuracy Report
  -## How to improve report
  -There're two parts of the report need to be improved if it has content.
  -* First part is `Failed Operations` which includes the schema validation errors for listed operations, all the errors are supposed to be fixed. From the error code you could browse to the linked document about the error defintion and fix tips.
  -* Second part is `Untested Operations` which includes the operations which don't have the traffic generated by RESTler for validation. It could be because the dependent operations fails in validation in which case please fix failed operation firstly so that this untested operation will be unlocked automatically.
  +The purpose of the Service Contract (Swagger) Accuracy Report is to ensure that service contracts accuractly reflect true service behavior. It is critical that the contract be accurate because we use it to produce many assets such as documentation, SDKs (in many programming languages), and tools (Azure CLI & PowerShell). When the contract is incorrect, these assets are broken and fixing the contract later causes breaking changes and significant pain to all our customers.
  -## How to improve Untested Operations
  -All the traffics for each operation are generated by RESTler automatically, if the result says the operation is untested then you could try to modify RESTler config files to improve RESTler generation coverage.
  -[@Marina to add details on how to modify configs]
  +Our tooling ([RESTler](https://github.com/microsoft/restler-fuzzer)) that produces this report tests all service operations and compares the actual requests/responses against the contract for accuracy.
  -* Download and modify each RESTler config
  -[to add details]
  +***
  +**IMPORTANT: _All operations must be tested and pass before the PR contract can be merged._**
  +***
  -* Debug locally with updated RESTler configs
  -[to add details]
  +For any `Failed Operations`, use the error information (and links provided) to either fix the contract or fix the service behavior. Fix failed operations first as this may enable our tooling to test some of the currently untested operations.
  -* Check in updated RESTler configs to be used in swagger PR pipeline and re-run
  -[to add details]
  +For any `Untested Operations`, you must improve the RESTler configuration files:
  + 1. Download the RESTler configuation file
  + - ...
  + 2. Modify the configuration file
  + - ...
  + 3. Debug your configuration file changes locally
  + - ...
  + 4. Upload the modified conf file so the PR pipeline can use it and re-run the Service Contract Accuracy report
  + - ...
  