more broken links

Author: davemooreuws

cypress/e2e/broken-links.cy.ts

@@ -85,7 +85,7 @@ describe('Broken links test suite', () => {
             cy.log(`link already checked`)
             expect(VISITED_SUCCESSFUL_LINKS[url]).to.be.true
           } else {
-            cy.wait(100)
+            cy.wait(25)
 
             req(url).then((res: Cypress.Response<any>) => {
               let acceptableCodes = CORRECT_CODES

docs/guides/nodejs/uptime.mdx

@@ -541,7 +541,7 @@ We are ready to play with our new uptime monitoring app! Navigate to http://loca
 
 ### Deployment
 
-As a next step, [deploy](/get-started/deployment) your app to the cloud of your choice.
+As a next step, [deploy](/get-started/foundations/deployment) your app to the cloud of your choice.
 
 ## Conclusion
 

docs/misc/contributions.mdx

@@ -16,7 +16,7 @@ Join the conversation about Nitric-related topics in the [Nitric repository on G
 
 Your feedback and ideas are incredibly helpful to keep improving Nitric. If you encounter any issues or have suggestions for new features, please create a [bug report](https://github.com/nitrictech/nitric/issues) or submit a [feature request](https://github.com/nitrictech/nitric/issues/new?template=feature_request.md).
 
-For detailed instructions on reporting bugs, refer to the [Creating Bug Reports guide](/support#bug-reports).
+For detailed instructions on reporting bugs, refer to the [Creating Bug Reports guide](/misc/support#bug-reports).
 
 ## Areas to Jump In
 

docs/misc/faq.mdx

@@ -20,7 +20,7 @@ Nitric helps with code and application portability across cloud providers and th
 
 Nitric is designed for extensibility so you're never restricted. For services/APIs/etc. that aren't supported, you'll continue to be able to directly target those services in your code. While this may result in coupling between applications and cloud providers, continuing to use the bulk of Nitric's APIs keeps that to a minimum.
 
-Additionally, being an Open Source project, you're welcome to [contribute](/contributions) additional services and plugins to the Nitric project to permanently add support for these integrations.
+Additionally, being an Open Source project, you're welcome to [contribute](/misc/contributions) additional services and plugins to the Nitric project to permanently add support for these integrations.
 
 ## How do I view my deployments on the Pulumi dashboard?
 

docs/providers/custom/create.mdx

@@ -6,7 +6,7 @@ description: 'How to build a custom provider using Nitric'
 
 This guide is for those that are interested in building their own custom provider to target a new cloud, implement their own internal development platform, or just curious to know how it all works. Nitric's main goal is to keep a general interface for interacting with cloud resources, regardless of the provider. This abstraction enables portability, developer efficiency, and standardizes the way that code is written across teams.
 
-This guide assumes you understand the basis of the Nitric [providers](/providers). If you are looking to just replace one or two resources from a standard provider, consider looking at the documentation [here](./extend-standard-provider).
+This guide assumes you understand the basis of the Nitric [providers](/providers). If you are looking to just replace one or two resources from a standard provider, consider looking at the documentation [here](./extend).
 
 <Note>
   Our providers and helpers are written in Go, however our provider's are based

docs/providers/custom/extend.mdx

@@ -135,7 +135,7 @@ You'll notice that we also override the `Bucket` value to use the pulumi spaces
 
 ### Config
 
-Now we can create an extension configuration to allow adding digital ocean configuration to our stack file. You can find the base AWS configuration [here](../aws/configuration).
+Now we can create an extension configuration to allow adding digital ocean configuration to our stack file. You can find the base AWS configuration [here](../pulumi/aws/configuration).
 
 Start by defining the type of configuration we want. To deploy to digital ocean we require setting a Digital Ocean token as well as a spaces key, secret, and region.
 

docs/providers/pulumi/index.mdx

@@ -4,7 +4,7 @@ description: 'How Nitric integrates with Pulumi'
 
 # Nitric Pulumi Providers
 
-Nitric enables application portability and deployments through pluggable modules known as [providers](/get-started/foundations/providers). This allows applications to be deployed with many different Infrastructure Automation technologies, including [Pulumi](https://pulumi.com). Nitric has pre-built providers that use Pulumi to deploy to [AWS](/providers/pulumi/aws), [Azure](/providers/pulumi/azure) and [Google Cloud](/providers/pulumi/gcp).
+Nitric enables application portability and deployments through pluggable modules known as [providers](/get-started/foundations/deployment#providers). This allows applications to be deployed with many different Infrastructure Automation technologies, including [Pulumi](https://pulumi.com). Nitric has pre-built providers that use Pulumi to deploy to [AWS](/providers/pulumi/aws), [Azure](/providers/pulumi/azure) and [Google Cloud](/providers/pulumi/gcp).
 
 <Note>
   All pre-built Pulumi providers are [direct deployment

docs/providers/terraform/index.mdx

@@ -4,7 +4,7 @@ description: 'How Nitric integrates with Terraform'
 
 # Nitric Terraform Providers
 
-Nitric enables application portability and deployments through pluggable modules known as [providers](/get-started/foundations/providers). This allows applications to be deployed with many different Infrastructure Automation technologies, including [Terraform](https://www.terraform.io/). Nitric has pre-built providers that use Terraform to deploy to [AWS](/providers/terraform/aws) and [Google Cloud](/providers/terraform/gcp), with Azure support planned.
+Nitric enables application portability and deployments through pluggable modules known as [providers](/get-started/foundations/deployment#providers). This allows applications to be deployed with many different Infrastructure Automation technologies, including [Terraform](https://www.terraform.io/). Nitric has pre-built providers that use Terraform to deploy to [AWS](/providers/terraform/aws) and [Google Cloud](/providers/terraform/gcp), with Azure support planned.
 
 <Note>
   All pre-built Terraform providers are [IaC generating

docs/reference/cli.mdx

@@ -105,7 +105,7 @@ nitric start
 
 This will run the Nitric server for local testing. This will output local endpoints for your apis and open the [local dashboard](/get-started/foundations/projects/local-development) for testing.
 
-For more information on local development, see the [local development](/reference/cli/local-development) docs.
+For more information on local development, see the [local development](/get-started/foundations/projects/local-development) docs.
 
 ## Deployment
 

docs/reference/languages.mdx

@@ -18,8 +18,8 @@ The following runtimes are currently supported or are in development:
 | [Python](/reference/python)  | Full Support | [https://github.com/nitrictech/python-sdk](https://github.com/nitrictech/python-sdk) |
 | [Go](/reference/go)          | Full Support | [https://github.com/nitrictech/go-sdk](https://github.com/nitrictech/go-sdk)         |
 | [Dart](/reference/dart)      | Experimental | [https://github.com/nitrictech/dart-sdk](https://github.com/nitrictech/dart-sdk)     |
-| [C#](/reference/csharp)      | v0 Support   | [https://github.com/nitrictech/dotnet-sdk](https://github.com/nitrictech/dotnet-sdk) |
-| [JVM](/reference/jvm)        | v0 Support   | [https://github.com/nitrictech/jvm-sdk](https://github.com/nitrictech/jvm-sdk)       |
+| [C#](/reference/csharp/v0)   | v0 Support   | [https://github.com/nitrictech/dotnet-sdk](https://github.com/nitrictech/dotnet-sdk) |
+| [JVM](/reference/jvm/v0)     | v0 Support   | [https://github.com/nitrictech/jvm-sdk](https://github.com/nitrictech/jvm-sdk)       |
 
 If a language you want isn't listed, come chat with us on [Discord](https://nitric.io/chat).