fix links

src/markdown-pages/docs/manage-ecosystem/runs-prepare.md

@@ -5,7 +5,7 @@ title: "Selecting tests to run in an Ecosystem"
 
 If you have a group of tests that you want to run in batch, the simplest way to do this is by defining these tests inside a portfolio. You can create a portfolio of tests by using the `runs prepare` command. You can build the portfolio from single or multiple [test streams](https://galasa.dev/docs/writing-own-tests/test-streams).
 
-This portfolio of tests can then be run by using the [runs submit command](/docs/cli-command-reference/ecosystem-cli-runs-submit). When you submit the tests to run, you need specify only the portfolio name on the command, rather than listing all of the classes.
+This portfolio of tests can then be run by using the [runs submit command](/docs/manage-ecosystem/ecosystem-cli-runs-submit). When you submit the tests to run, you need specify only the portfolio name on the command, rather than listing all of the classes.
 
 ## Working with the `runs prepare` command
 

src/markdown-pages/docs/manage-ecosystem/runs-submit.md

@@ -5,15 +5,15 @@ title: "Running tests in an Ecosystem"
 
 The `runs submit` command submits and monitors tests in the Galasa Ecosystem. Tests can be input either from a portfolio or directly from a test package.
 
-For information about creating a portfolio by using the Galasa CLI, see the documentation for the [runs prepare](/docs/cli-command-reference/ecosystem-cli-runs-prepare) command.
+For information about creating a portfolio by using the Galasa CLI, see the documentation for the [runs prepare](/docs/manage-ecosystem/ecosystem-cli-runs-prepare) command.
 
 ## Working with the `runs submit` command
 
 The following section provides a subset of examples of how you can use the `runs submit` command to complete various tasks, for example, getting help, submitting tests, and setting overrides. The examples build on the Galasa SimBank tests, which you can run non-locally if you have an ecosystem that is running SimPlatform.
 
 ### Submitting tests to an ecosystem from a portfolio
 
-The following example assumes that you have created a `my_portfolio.yaml` portfolio by using the [runs prepare](/docs/cli-command-reference/ecosystem-cli-runs-prepare) command. The command submits tests from the `my_portfolio.yaml` portfolio, and specifies the following settings.
+The following example assumes that you have created a `my_portfolio.yaml` portfolio by using the [runs prepare](/docs/manage-ecosystem/ecosystem-cli-runs-prepare) command. The command submits tests from the `my_portfolio.yaml` portfolio, and specifies the following settings.
 
 On Mac or Unix:
 

src/markdown-pages/docs/writing-own-tests/setting-up-galasa-project.md

@@ -226,7 +226,7 @@ The following extract from the generated parent pom.xml shows some of the key el
 <packaging>pom</packaging>
 ```
 
-- The `<groupId>` is used to group related Maven projects in a Maven repository. It is recommended (but not enforced) that all projects in a [test stream](../writing-own-tests/test-streams) share the same `groupId`.
+- The `<groupId>` is used to group related Maven projects in a Maven repository. It is recommended (but not enforced) that all projects in a [test stream](../manage-ecosystem/test-streams) share the same `groupId`.
 - The `<artifactId>` must be unique for each Maven project under a `groupId`. To prevent confusion, you could make it unique across `groupId`s. The `groupId` and `artifactId` can nominally be anything you choose, but if you were to ever consider publishing the project on Maven Central, you would have to ensure that they were unique across Maven Central. Because of this, and to avoid future name collisions, it is conventional to use (reversed) company domain names, which leads to patterns like `dev.galasa.example.banking`.
 - The `<version>` in this project is set to `0.1.0-SNAPSHOT`. 
 - `<packaging>` indicates what type of Maven project this is - in this case, a `pom` project.