Grammar fixup.

Author: dobooth

docs/credentials.md

@@ -55,7 +55,7 @@ magento/carriers_usps_password=Lmgxvrq89uPwECeV
 ....
 ```
 
-Or add new key & value pairs for your own credentials. The keys use the following format:
+Or add new key/value pairs for your own credentials. The keys use the following format:
 
 ```conf
 <vendor>/<key_name>=<key_value>
@@ -150,16 +150,16 @@ Define the value as a reference to the corresponding key in the credentials file
 
 -  `_CREDS` is an environment constant pointing to the `.credentials` file
 -  `my_data_key` is a key in the the `.credentials` file or vault that contains the value to be used in a test step
-  - for File Storage, ensure your key contains the vendor prefix, i.e. `vendor/my_data_key`
-  - for Vault Storage, ensure your key contains your secret basepath + `/mftf/` + your vendor prefix + `/` and finally your key, i.e. `secret/mftf/vendor/my_data_key`
+   - for File Storage, ensure your key contains the vendor prefix, i.e. `vendor/my_data_key`
+   - for Vault Storage, ensure your key contains your secret basepath + `/mftf/` + your vendor prefix + `/` and finally your key, i.e. `secret/mftf/vendor/my_data_key`
 
 For example, to reference secret data in the [`fillField`][] action, use the `userInput` attribute using a typical File Storage:
 
 ```xml
 <fillField stepKey="FillApiToken" selector=".api-token" userInput="{{_CREDS.vendor/my_data_key}}" />
 ```
 
-... whereas to do the same using Vault Storage:
+To do the same using Vault Storage:
 
 ```xml
 <fillField stepKey="FillApiToken" selector=".api-token" userInput="{{_CREDS.secret/mftf/vendor/my_data_key}}" />