Upgrade all workflows to actions/checkout@v2 (#2013)

* Upgrade all workflows to actions/checkout@v2
* fix markdown issue

.github/workflows/checkLinks.yml

@@ -13,7 +13,7 @@ jobs:
  runs-on: ubuntu-latest
  steps:
  - name: Checkout
- uses: actions/checkout@v1
+ uses: actions/checkout@v2
  with:
  fetch-depth: 1
  - name: link-check

.github/workflows/checkLint.yml

@@ -7,11 +7,11 @@ jobs:
  runs-on: ubuntu-latest
  steps:
  - name: Checkout
- uses: actions/checkout@v1
+ uses: actions/checkout@v2
  with:
  fetch-depth: 1
  - name: markdownlint-cli
- uses: nosborn/github-action-markdown-cli@9fc95163471d6460c35cccad13645912aaa25d5f
+ uses: nosborn/github-action-markdown-cli@v2.0.0
  with:
  files: Document
  config_file: ".markdownlint.json"

.github/workflows/docgenerator.yml

@@ -10,7 +10,7 @@ jobs:
  generate:
  runs-on: ubuntu-latest
  steps:
- - uses: actions/checkout@v1
+ - uses: actions/checkout@v2
  with:
  fetch-depth: 1
 

Document/0x06d-Testing-Data-Storage.md

@@ -222,12 +222,12 @@ A misconfigured Firebase instance can be identified by making the following netw
 
 `https://\<firebaseProjectName\>.firebaseio.com/.json`
 
-The _firebaseProjectName_ can be retrieved from the property list(.plist) file. For example, _PROJECT_ID_ key stores the corresponding Firebase project name in _GoogleService-Info.plist_ file.
+The _firebaseProjectName_ can be retrieved from the property list(.plist) file. For example, `PROJECT_ID` key stores the corresponding Firebase project name in _GoogleService-Info.plist_ file.
 
 Alternatively, the analysts can use [Firebase Scanner](https:/shivsahni/FireBaseScanner "Firebase Scanner"), a python script that automates the task above as shown below:
 
 ```bash
-python FirebaseScanner.py -f <commaSeperatedFirebaseProjectNames>
+python FirebaseScanner.py -f <commaSeparatedFirebaseProjectNames>
 ```
 
 #### Realm databases