Update README

README.md

@@ -50,7 +50,7 @@ Provisioning existing machines:
 
     If you wish to set or remove custom resource ID mapping scheme used by `evidence-collector`, you can change mapped values inside `/environments/full-setup/resource-id-map.json`.
 
-    See [Evidence collector's documentation](https://git.code.tecnalia.com/medina/wp3/task_3.2/evidence-collector) for more information.
+    See [Evidence collector's documentation](https://git.code.tecnalia.com/medina/public/wazuh-vat-evidence-collector) for more information.
 
     > Note: neither of these two files has to be changed for `security-monitoring` to work. You can (and should; in case of `.env`) leave them unchanged. 
 
@@ -197,7 +197,7 @@ Wazuh manager and Evidence collector should be installed on the same, clean mach
 
     `development.env` file includes local development and testing pre-configuration while `production.env` already includes settings for Evidence collector to connect to K8s deployed Clouditor.
 
-    See [Evidence collector's documentation](https://git.code.tecnalia.com/medina/wp3/task_3.2/evidence-collector) for more information.
+    See [Evidence collector's documentation](https://git.code.tecnalia.com/medina/public/wazuh-vat-evidence-collector) for more information.
 
     If you're installing both Evidence collector as well as Wazuh manager on the same machine (as intended), you have to set only `clouditor_host`, `elastic_host` & `wazuh_host` variables (where `elastic_host` & `wazuh_host` are the same).