INFRA-13814 Align parameter description with latest docs

Author: Leong Hui Wong

docs/using-the-api.md

@@ -41,18 +41,18 @@ The following parameters should be used:
 | rf2DeltaOnly | false | This is set to true when a [delta release](https://confluence.ihtsdotools.org/display/DOCGLOSS/delta+release) is being validated. This should be false if validating a [snapshot release](https://confluence.ihtsdotools.org/display/DOCGLOSS/snapshot+release). |
 | writeSuccesses | false | This indicates on whether the final report should list the successes. Due to the large amount of data in the international RF2 files, this should be generally set to false. |
 | groups | `<assertion_groups>` | The assertion groups to run as part of the validation, shown [above](#select-assertions) . You can list a different group if required, and separate multiple groups using commas. For most cases, first-time-common-edition **or** common-edition **or** common-authoring would be the ones to choose from. |
-| previousRelease | `<previous_release>` | Leave it empty when validating without previous release (i.e using assertion group first-time-common-edition) Otherwise enter the previous release version identified by the filename of the release you have previously uploaded (using the example above, this could be `SNOMEDCT_RF2_20200301T110000Z.zip`) |
-| dependencyRelease | `<dependency_release>` | The dependent International release version file name (e.g `SnomedCT_InternationalRF2_PRODUCTION_20190731T120000Z.zip`) used for validating extensions only. This is the name of the file used for the release first uploaded and listed at <http://localhost:8081/api/releases>. Note: Leave this empty when validating the international release files.|
+| previousRelease | `<previous_release>` | Leave it empty when validating without previous release (i.e using assertion group first-time-common-edition) Otherwise enter the previous release version identified by the filename of the release you have previously downloaded (using the example above, this could be `SNOMEDCT_RF2_20200301T110000Z.zip`) |
+| dependencyRelease | `<dependency_release>` | The dependent International release version file name (e.g `SnomedCT_InternationalRF2_PRODUCTION_20190731T120000Z.zip`) used for validating extensions only. Note: Leave this empty when validating International release files.|
 | runId | `<numeric identifier>` | Enter either the timestamp for point that this validation is being run or any numeric identifier to be used to identify the job (e.g. `2020090101`). |
-| storageLocation | `<sub_foldername>` | The folder where validation reports will be saved to. This needs to have a value and the rvf application must have permissions to write to this location. eg. `int/20190131/test` or `/tmp` |
+| storageLocation | `<sub_foldername>` | The folder where validation reports will be saved to. This needs to have a value and the rvf application must have permissions to write to this location. e.g. `int/20190131/test`|
 
-Please ensure that the releases specified in the parameters (e.g. _previousRelease_, _dependencyRelease_, and _previousDependencyEffectiveTime_) are made available to RVF [as described here](download-published-releases.md).
+Before starting the validation job, please ensure that the release packages (.zip) specified in the parameters (i.e. _previousRelease_, _dependencyRelease_, and _previousDependencyEffectiveTime_) are downloaded [as described here](download-published-releases.md).
 
-Once those have been entered, then submit the post and wait. The validation is likely to take some time but the job status can be found via the results URL. The URL of these RVF validation results can be found in the response location header parameter:
+Once the parameters have been entered, submit the POST request and wait. The validation is likely to take some time but the job status can be found via the results URL. The URL of these RVF validation results can be found in the response location header parameter:
 
-e.g `:"location": "http://localhost:8081/api/result/201905010901?storageLocation=int/20190131/test"`
+e.g. `:"location": "http://localhost:8081/api/result/201905010901?storageLocation=int/20190131/test"`
 
-When complete,the results report is returned, formated in JSON at the same URL.
+When complete,the results report is returned, formatted in JSON at the same URL.
 
 Examples
 --------