Update README.md

README.md

@@ -1,7 +1,6 @@
 # Data Space Connector Building Blocks
 
 - [Data Space Connector Building Blocks](#data-space-connector-building-blocks)
-  - [ToDo](#todo)
   - [Introduction](#introduction)
   - [Public Artifacts](#public-artifacts)
     - [Configuration of the Connector Image](#configuration-of-the-connector-image)
@@ -16,13 +15,6 @@
 > [!CAUTION]
 > Please note that most of the code in this repository is still a work in progress and will thus likely go through several breaking changes throughout its development.
 
-## ToDo
-
-- [ ] Finalise the design of our authentication extension, which will be based on W3C Verifiable Credentials (VC) and Decentralised Identifiers (DID).
-- [ ] Improve the documentation to demonstrate the integration of W3C VC and DID into the deployment process.
-- [ ] Remove the need to use PKCS12 keystores in production.
-- [ ] Consider writing additional examples of deployment.
-
 ## Introduction
 
 This repository contains a collection of software components that aim at simplifying the deployment of data space connectors based on the [Eclipse Dataspace Components](https://eclipse-edc.github.io/docs/#/) (EDC) ecosystem and the interactions of applications with those connectors. Specifically, the following components are provided here:
@@ -79,6 +71,15 @@ The example in this section will illustrate the following scenario:
 
 ### Configuration and Deployment
 
+> [!IMPORTANT]
+> The default configuration of the example relies on `host.docker.internal` resolving to the host IP address. However, this may not be the case if you're using Linux. If that's the case, please ensure that `host.docker.internal` is added to your `/etc/hosts` file:
+> ```
+> vagrant@vagrant:~/connector-building-blocks/edcpy$ cat /etc/hosts
+> 127.0.0.1 localhost
+> 127.0.1.1 vagrant
+> 127.0.0.1 host.docker.internal
+> ```
+
 #### Provider
 
 First, we will deploy the services of the provider participant.