Resolve "Refer to perl nms common"

Closes #10 (closed) and Closes #8 (closed)

README.md

 # Best practices
 
+There is no such thing as Best practices. Nothing can be best for everyone, everywhere. 
+This repo can therefore only be improved to become better than before. And it's already a lot
+
+Also don't miss
+* [CI best practices](https://code.europa.eu/digit-c4/dev/ci-best-practices)
+* [Python best practices](https://code.europa.eu/digit-c4/dev/python-best-practices)
+* ...
+and many more. See the [full list usint the `best-practices` topic](https://code.europa.eu/explore/projects/topics/best-practices)
+
 ## Local Workspace
 > Git tracked directories shouldn't be backup-ed using
 > another tool. All projects should therefore be stored
@@ -16,6 +25,10 @@ Example local file organization
 | | - opt/SNet/scm/opt
 | | | - opt_lib           # <== a repository in the legagy git
 | ...
+| - sdlc.***.europa.eu/
+| | - c4/
+| | | - shared/
+| ...
 | – code.europa.eu/       # <== hostname of the registry
 | | - digit-c4/           # <== gitlab group = folder
 | | | - dev/
@@ -26,8 +39,11 @@ Example local file organization
 PROJECT_HOME="~/Workspace/code.europa.eu/digit-c4/dev/best-practices"
 mkdir -p $(dirname $PROJECT_HOME) 
 git clone git@code.europa.eu:digit-c4/dev/best-practices.git $PROJECT_HOME \
-  && cd $PROJECT_HOME \
-  && git submodule update --init --recursive
+  && cd $PROJECT_HOME
+```
+Also don't forget to sync gitmodules
+```shell
+git submodule update --init --recursive
 ```
 
 ### HTTPS Gitlab git credentials
@@ -166,6 +182,7 @@ export LOG_LEVEL=INFO
 ### Known libraries
 The dev team is maintaining a set of libraries to standardise the logging output
 * [Python NMS Common](https://code.europa.eu/digit-c4/dev/python-nms-common/)
+* [Perl NMS Common](https://code.europa.eu/digit-c4/dev/perl-nms-common)
 
 ## Inspiring trainings, documents, videos, etc
 * [Static, Unit, Integration, and End-to-End Tests Explained](https://www.youtube.com/watch?v=TLccnKIMggA)