diff --git a/docs/contributing/02-maintainers/050-operations.md b/docs/contributing/02-maintainers/050-operations.md index 1796e853310..aa56f3d2a24 100644 --- a/docs/contributing/02-maintainers/050-operations.md +++ b/docs/contributing/02-maintainers/050-operations.md @@ -59,7 +59,7 @@ If not automated, the responder should create a thread in the #alert channel in ### Response If possible, immediate action should be taken to mitigate the issue. -A [runbook](./10-runbooks/) should be followed if one exists. +A [runbook](/contributing/category/runbooks) should be followed if one exists. Otherwise, the responder should take the best action they can to mitigate the issue. For P0/P1 issues based on regressions, the default behavior should be to revert to the last known good version. Make sure to document any actions taken as this will be extremely helpful in building a good post-mortem and runbook if needed. diff --git a/docs/contributing/999-rfcs/2022-06-14-polycons.md b/docs/contributing/999-rfcs/2022-06-14-polycons.md index 23b327cea37..a6142f2c442 100644 --- a/docs/contributing/999-rfcs/2022-06-14-polycons.md +++ b/docs/contributing/999-rfcs/2022-06-14-polycons.md @@ -4,7 +4,7 @@ description: This document describes a dependency injection meta-framework for p --- > Note: the design of polycons has changed significantly since this was first written! -> Please check out the polycons [README](https://github.com/winglang/polycons) for details about how the current Polycons API works, and check the [SDK Architecture](/wingsdk#sdk-architecture) to see where many ideas from this RFC were adopted! +> Please check out the polycons [README](https://github.com/winglang/polycons) for details about how the current Polycons API works, and check the [SDK Architecture](../start-here/wingsdk#sdk-architecture) to see where many ideas from this RFC were adopted! * **Author(s):**: @MarkMcCulloh * **Submission Date**: 2022-06-14 diff --git a/docs/contributing/999-rfcs/2023-06-12-language-spec.md b/docs/contributing/999-rfcs/2023-06-12-language-spec.md index 89fc32b3815..e5f50409794 100644 --- a/docs/contributing/999-rfcs/2023-06-12-language-spec.md +++ b/docs/contributing/999-rfcs/2023-06-12-language-spec.md @@ -16,7 +16,7 @@ are still not implemented (see [project board](https://github.com/orgs/winglang/ ### 0.1 Motivation -The Wing Programming Language (aka winglang[RFC](/2022-05-28-winglang-reqs)) is a general +The Wing Programming Language (aka winglang[RFC](./2022-05-28-winglang-reqs)) is a general purpose programming language designed for building applications for the cloud. What makes Wing special? Traditional programming languages are designed around diff --git a/docs/docs/02-concepts/05-simulator.md b/docs/docs/02-concepts/05-simulator.md index 39a019246fe..2ddc73fdc00 100644 --- a/docs/docs/02-concepts/05-simulator.md +++ b/docs/docs/02-concepts/05-simulator.md @@ -5,7 +5,7 @@ description: A facility for executing Wing applications on the local machine for keywords: [Wing simulator, simulator] --- -The simulator is a [compiler target](./05-compile-targets.md) that comes +The simulator is a [compiler target](./03-compile-targets.md) that comes provided in Wing for testing applications locally. The simulator does not require you to deploy resources to any cloud providers. Since it's a simulation, the simulator does not provide the same guarantees as running your application @@ -30,7 +30,7 @@ is provided below. To use the simulator, you will need a Wing program that has beem compiled to the simulator (with `wing compile --target sim `). -Check out the [Wing Getting Started Guide](/) for more information on how to write your +Check out the [Wing Getting Started Guide](/docs) for more information on how to write your first Wing program. The output will typically be located in the `target` directory of your Wing project, diff --git a/docs/docs/06-tools/01-cli.md b/docs/docs/06-tools/01-cli.md index 01a3a4bb861..6cf5ee3bc9e 100644 --- a/docs/docs/06-tools/01-cli.md +++ b/docs/docs/06-tools/01-cli.md @@ -157,7 +157,7 @@ Additionally the `compile` command can be provided an optional list of plugins t $ wing compile --target tf-aws ENTRYPOINT.w --plugins PLUGIN1 PLUGIN2 ``` Each plugin can be an absolute paths or relative path to a JavaScript file. For more -on how to create a plugin, see [Compiler Plugins](/reference/compiler-plugins). +on how to create a plugin, see [Compiler Plugins](./compiler-plugins). ## Test: `wing test`