fix broken links (#385)

microsoft · Apr 21, 2020 · 4361882 · 4361882
1 parent 803773f
commit 4361882
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/devops/providers/azure-devops/README.md b/devops/providers/azure-devops/README.md
@@ -14,7 +14,7 @@ Please visit the following page for an overview of the Infrastructure Template r
 - **[Azure Service Principal (Service Connection)](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal)**
 
   This will be needed in order to provide the deployment templates the appropriate permissions to deploy infrastructure within an Azure subscription.
-  - See Step 2 and 3 from [Getting Started - Advocated Pattern Owner](../GETTING_STARTED_ADD_PAT_OWNER.md) ("_Provision Azure resources needed for Azure Devops pipeline_")/ ("Configure Azure Devops pipeline using Azure resource values") for more information.
+  - See Step 2 and 3 from [Getting Started - Advocated Pattern Owner](../../../docs/GETTING_STARTED_ADD_PAT_OWNER.md) ("_Provision Azure resources needed for Azure Devops pipeline_")/ ("Configure Azure Devops pipeline using Azure resource values") for more information.
   - Also see [Variable Group Overview](###Variable-Group-Overview) of this document for account setup naming recommendations.
 
 - **[Azure Storage Account and Backend State Container](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview)**

diff --git a/docs/GETTING_STARTED_COBALT_DEV.md b/docs/GETTING_STARTED_COBALT_DEV.md
@@ -61,9 +61,9 @@ The easiest way to try Cobalt is to start with our [hello-world](https://github.
 
 Setting up a cobalt deployment comprises of 5 general steps.
 
-1. You can follow these [instructions](devops/providers/azure-devops/README.md) to create an cloud-based CI pipeline definition.
+1. You can follow these [instructions](../devops/providers/azure-devops/README.md) to create an cloud-based CI pipeline definition.
 2. Our cloud deployment templates provide an configurable default setup intended for a t-shirt sized environment scenario. Pick the template folder most relevant to your use-case as a starting point. Each template folder is shipped with setup instructions.
 3. It's important to implement quality assurance that validates E2E functional assertions against your infrastructure resources. Each template comes pre-packaged with some basic integration and unit tests. We encourage you to define integration tests in the `test/integration` folder of your template that's specific to your use-case.
-4. Follow these [instructions](test-harness/README.md) to setup your local environment. Make sure that the repository lives in a directory that does not live within `$GOPATH`.
+4. Follow these [instructions](../test-harness/README.md) to setup your local environment. Make sure that the repository lives in a directory that does not live within `$GOPATH`.
 5. Create a new local git branch and commit your changes. Run the test harness on your localhost via `./test-harness/local-run.sh`.