Small updates of README.md

README.md

@@ -193,12 +193,12 @@ Testing frontend changes with the test webapp
 ---------------------------------------------
 
 * Start the backend using `frank-runner/specials/ladybug` as explained at [Backend development](#backend-development). This is without `test.with.iaf`. Wait until Tomcat is up and running.
-* Execute command `pnpm ng serve` from within the `ladybug-frontend` checkout. This wil make Node.js serve the Ladybug frontend files and proxy the Ladybug backend api as the src folder contains a proxy.conf.json (this will circumvent CORS related problems as the frontend served by Node.js on port 4200 would call the api on port 80). It is now possible to use both the real frontend that is eventually seen by end users (on port 80) and the Ladybug frontend served by Node.js (on port 4200). The page on the following url (also mentioned above) contains links to both frontends: `http://localhost`.
+* Execute command `pnpm start` or `pnpm ng serve` from within the `ladybug-frontend` checkout. This will make Node.js serve the Ladybug frontend files and proxy the Ladybug backend api as the src folder contains a proxy.conf.json (this will circumvent CORS related problems as the frontend served by Node.js on port 4200 would call the api on port 80). It is now possible to use both the real frontend that is eventually seen by end users (on port 80) and the Ladybug frontend served by Node.js (on port 4200). The page on the following url (also mentioned above) contains links to both frontends: `http://localhost`.
 
 Testing frontend changes with Frank!Framework
 ---------------------------------------------
 
-The Frank!Framework incorporates Ladybug and configures it a bit different then the test webapp. It for example adds a Gray box view which you might want to test. The Frank!Framework serves the Ladybug on a different url then the test webapp so you need to configure the previously mentioned proxy a bit different and change the url in `src/proxy.conf.json` from http://localhost/ladybug to http://localhost/iaf/ladybug. You can do this by copying `src/proxy.ff.conf.json` to `src/proxy.conf.json`. In case you also have backend changes you can start the Frank!Framework as eplained above (with `test.with.iaf=true`). Otherwise it is easier to for example run Frank2Example1. See the Frank!Runner [README.md](https://github.com/wearefrank/frank-runner#frankrunner) for more information on how to start a Frank2Example1 or another Frank.
+The Frank!Framework incorporates Ladybug and configures it a bit different then the test webapp. It for example adds a Gray box view which you might want to test. The Frank!Framework serves the Ladybug on a different url than the test webapp. If you want to run the Ladybug frontend in combination with the Frank!Framework, start it using `pnpm startWithFF`. Alternatively, you can run the Maven build of the ladybug frontend and adjust the backend's `pom.xml` locally to reference your locally built ladybug-frontend artifact. In case you also have backend changes you can start the Frank!Framework as eplained above (with test.with.iaf=true). Otherwise it is easier to for example run Frank2Example1. See the Frank!Runner [README.md](https://github.com/wearefrank/frank-runner#frankrunner) for more information on how to start a Frank2Example1 or another Frank.
 
 Testing frontend changes with unit tests
 ----------------------------------------