diff --git a/.github/workflows/pysh-check.yml b/.github/workflows/pysh-check.yml
index 1226920..40ae429 100644
--- a/.github/workflows/pysh-check.yml
+++ b/.github/workflows/pysh-check.yml
@@ -21,4 +21,6 @@ jobs:
         with:
           repository: 'PelionIoT/scripts-internal'
           token: ${{ secrets.ACCESS_TOKEN }}
+          path: 'scripts-internal'
+      - run: touch scripts-internal/.pyshcheck
       - run: ../scripts-internal/pysh-check/pysh-check.sh --workdir .
diff --git a/README.md b/README.md
index 56f116b..18cfb6f 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@ You can view the API documentation (swagger) for the pep-server via http://local
 
 ## Tests
 
-Run `factory-configurator-client-example`, if it is not installed, follow [the document about building the FCC example on native Linux](https://developer.izumanetworks.com/docs/device-management-provision/latest/ft-demo/building-demo.html#native-linux) for the detailed steps. Below are the quick steps that install the program. For example, in the []`meta-edge`](https://github.com/PelionIoT/meta-edge) project you can find the precompiled binary located at `/edge/system/bin/factory-configurator-client-armcompiled.elf`.
+Run `factory-configurator-client-example`, if it is not installed, follow [the document about building the FCC example on native Linux](https://developer.izumanetworks.com/docs/device-management-provision/latest/ft-demo/building-demo.html#native-linux) for the detailed steps. Below are the quick steps that install the program. For example, in the [`meta-edge`](https://github.com/PelionIoT/meta-edge) project you can find the precompiled binary located at `/edge/system/bin/factory-configurator-client-armcompiled.elf`.
 
 <span class="notes">**Note:** This tool is not supported on macOS, so if you are running the server on macOS, you can't test pep CLI on the same machine.</span>