fix(trg): typos, formatting and correct links

docs/release/trg-4/trg-4-06.md

@@ -76,7 +76,7 @@ As for any pre-built image usage, it is the image user's responsibility to ensur
 
 ## Best practice and examples
 
-- Use "Container images" as headline to link to the container image notice files
+- Use "Container images" as headline to link to the container image notice files from the repositories README.md file
 - Name the notice file "notice.md"
 - Provide important information about your image with your notice. Examples:
   - Available volumes
@@ -88,7 +88,7 @@ Keeping the DockerHub description up-to-date with the latest notice content is c
 The following workflow step can be used as part of the DockerHub publishing workflow to ensure that:
 
 ```yaml
-# DockerHub publishing worklflow 
+# DockerHub publishing worklflow
 
 ...
 
@@ -110,7 +110,7 @@ The following workflow step can be used as part of the DockerHub publishing work
 The following examples are shown as reference, to see already existing and complete versions of a 'Notice for docker images'.
 They **can not** be used for your product without modifications.
 
-- [edc-controlplane-memory-hashicorp-vault](https://github.com/eclipse-tractusx/tractusx-edc/edit/main/edc-controlplane/edc-controlplane-memory-hashicorp-vault/notice.md)
+- [edc-controlplane-memory-hashicorp-vault](https://github.com/eclipse-tractusx/tractusx-edc/blob/main/edc-controlplane/edc-controlplane-memory-hashicorp-vault/notice.md)
 - [Country Risk](https://github.com/eclipse-tractusx/vas-country-risk/blob/main/DOCKER_NOTICE.md)
 
 ## Already collected base image information