Merge pull request #241 from equinor/update-workflow-link

fixed linkes to Workflow from Radix Concepts and Reference

public-site/docs/src/docs/topic-concepts/index.md

@@ -20,7 +20,7 @@ The basic configuration for an application (the _application registration_) is c
 
 An environment is an isolated area where all of an application's [components](#component) run. It is meant to compartmentalise an instance of the application, and can be used to provide that instance to users.
 
-A typical setup is to create two environments, `development` and `production` — the former can be used for testing and showcasing features under development, and the latter is the "live" application that users rely on. Any (reasonable) number of environments is allowed in Radix; you can use these in a way that best fits your development and deployment [workflow](../../guides/workflows/).
+A typical setup is to create two environments, `development` and `production` — the former can be used for testing and showcasing features under development, and the latter is the "live" application that users rely on. Any (reasonable) number of environments is allowed in Radix; you can use these in a way that best fits your development and deployment [workflow](../../start/workflows/).
 
 Within an environment, components should address each other over the network by using just their names, instead of IP addresses or FQDNs. For instance, if you have two components, `api` and `worker` (listening on port 3000 for HTTP calls), the API can communicate with `http://worker:3000/some-endpoint`.
 

public-site/docs/src/references/reference-radix-config/index.md

@@ -88,7 +88,7 @@ The name of the environment. Can be `dev`, `qa`, `production` etc.
 
 ### `build`
 
-`from` specifies which branch each environment will build from. If `from` is not specified for the environment, no automatic builds or deployments will be created. This configuration is useful for a promotion-based [workflow](../../guides/workflows/).
+`from` specifies which branch each environment will build from. If `from` is not specified for the environment, no automatic builds or deployments will be created. This configuration is useful for a promotion-based [workflow](../../start/workflows/#promotion).
 
 Wildcard branch mapping is also support, using `*` and `?`. Examples: