chore: update and fix relative links (#12720)

Author: walidelnozahy

docs/guides/dashboard/README.md

@@ -39,7 +39,7 @@ For Serverless Framework's new Observability offering, you must use version 3.35
 
 If you don't already have a Serverless Framework account, create a new account at [https://app.serverless.com](https://app.serverless.com).
 
-If you don't have existing Serverless Framework Services, follow the [Getting Started with the Serverless Framework and AWS](/framework/docs/getting-started/) guide. This will help you get a Serverless Framework Service deployed to AWS, and enabled with the Dashboard.
+If you don't have existing Serverless Framework Services, follow the [Getting Started with the Serverless Framework and AWS](../../getting-started.md) guide. This will help you get a Serverless Framework Service deployed to AWS, and enabled with the Dashboard.
 
 If you have existing Serverless Framework Services, in the directory with your Service's `serverless.yml` file, run the `serverless` command. This will walk you through the setup process, including setting up your AWS account credentials and creating an organization and application from the Dashboard. Once completed, you'll notice that the `org` and `app` fields will be added to your `serverless.yml` to indicate the org/app to which this service belongs.
 

docs/guides/dashboard/cicd/README.md

@@ -39,7 +39,7 @@ Before you setup your CI/CD workflow, make sure you meet the following requireme
 
 As is the case with deployments from the Serverless Framework CLI, Serverless CI/CD requires access to your AWS Account in order to deploy your services. To make this process as secure as possible, Serverless CI/CD will generate short-lived credentials to your AWS account on each deployment. This is done by creating an AWS Access Role in your AWS account and associating it with a Provider in the Serverless Framework Dashboard.
 
-If you’ve already set up an AWS Access Role with a Provider, you can skip this step. Otherwise, please go through the instructions on our [Provider documentation page](../../dashboard/providers.md) to help set one up.
+If you’ve already set up an AWS Access Role with a Provider, you can skip this step. Otherwise, please go through the instructions on our [Provider documentation page](../dashboard/providers.md) to help set one up.
 
 ### Step 2: Connect to Github
 

docs/guides/dashboard/cicd/branch-deployments.md

@@ -29,4 +29,4 @@ To add a new branch deployment, in the "branch deploys" section of the CI/CD set
 
 ## Add a stage to a branch deployment
 
-If you are a first time user, the stage list may be empty. You must first [create a new deployment profile](/framework/docs/dashboard/profiles#creating-a-new-deployment-profile), and [add the deployment profile to a stage in your application](/framework/docs/dashboard/profiles#add-a-deployment-profile-to-your-application-and-stage). As mentioned in the requirements section, the deployment profile must also have an [AWS Access Role](/framework/docs/dashboard/access-roles/).
+You can assign a stage to each branch deployment, but ensure that a valid provider is set for this service.

docs/guides/dashboard/monitoring/metrics.md

@@ -81,11 +81,11 @@ saved as a shared views to collaborate with team mates on specific searches.
 - **Events** - Individual invocations may produce multiple errors or warnings.
   The Serverless SDK may also produce errors and warnings. Filtering by Events
   enables filtering for invocations which include any of the selected Event types.
-  You can find more details about Event types on the [Trace Explorer](./trace-explorer.md).
+  You can find more details about Event types on the [Trace Explorer](./traces#event-types.md).
 - **Cold start** - Filters for metrics on AWS Lambda invocations that were a
   cold start.
 - **Duration** - Filters based on the AWS Lambda response duration.
 - **Custom Tags** - Filters for metrics on invocations that had the provided
   custom tags. Custom tags on traces, errors, and warnings are all queried. Use
-  the [Node.js](../nodejs-sdk.md) or [Python](./python-sdk.md) Serverless SDK to
+  the [Node.js](./sdk/nodejs.md) or [Python](./sdk/python.md) Serverless SDK to
   set custom tags.

docs/guides/dashboard/monitoring/sdk/README.md

@@ -32,7 +32,7 @@ It also has certain features you can use directly in your lambda such as capturi
 ## Advanced Span Configuration
 
 For most of the SDK configuration, like turning on/off span collection, follow the
-[Monitoring Configuration](../monitoring/#configuration) instructions to modify your
+[Monitoring Configuration](../README.md/#configuration) instructions to modify your
 serverless.yml appropriately.
 
 If needed, you can configure HTTP span collection with the following environment variables

docs/guides/variables/README.md

@@ -40,19 +40,19 @@ You can define your own variable syntax (regex) if it conflicts with CloudFormat
 
 ## Current variable sources:
 
-- [Self-References Properties Defined in `serverless.yml`](/framework/docs/guides/variables/self)
-- [Serverless Core Variables](/framework/docs/guides/variables/core)
-- [Environment Variables](/framework/docs/guides/variables/env-vars)
-- [CLI Options](/framework/docs/guides/variables/cli-options)
-- [External YAML/JSON Files](/framework/docs/guides/variables/file)
-- [Dynamic Values from Javascript](/framework/docs/guides/variables/javascript)
-- [Git](/framework/docs/guides/variables/git)
-- [AWS-specific](/framework/docs/guides/variables/aws)
-- [AWS S3](/framework/docs/guides/variables/s3)
-- [AWS SSM Parameter Store & Secrets Manager](/framework/docs/guides/variables/ssm)
-- [AWS CloudFormation Outputs](/framework/docs/guides/variables/cf-stack)
-- [HashiCorp Terraform State Outputs](/framework/docs/guides/variables/terraform)
-- [HashiCorp Vault Secrets](/framework/docs/guides/variables/vault)
+- [Self-References Properties Defined in `serverless.yml`](./self)
+- [Serverless Core Variables](./core)
+- [Environment Variables](./env-vars)
+- [CLI Options](./cli-options)
+- [External YAML/JSON Files](./file)
+- [Dynamic Values from Javascript](./javascript)
+- [Git](./git)
+- [AWS-specific](./aws)
+- [AWS S3](./s3)
+- [AWS SSM Parameter Store & Secrets Manager](./ssm)
+- [AWS CloudFormation Outputs](./cf-stack)
+- [HashiCorp Terraform State Outputs](./terraform)
+- [HashiCorp Vault Secrets](./vault)
 
 ## Recursively reference properties
 

docs/guides/workflow.md

@@ -79,7 +79,7 @@ serverless deploy function -f [FUNCTION NAME] -s [STAGE NAME] -r [REGION NAME]
 
 Use this to easily develop your AWS Lambda Functions locally. This will run your AWS Lambda Functions locally and allow you to send events to them on AWS.
 
-Currently this is only supported for Node.js. Learn more about the [dev command](/framework/docs/providers/aws/cli-reference/dev).
+Currently this is only supported for Node.js. Learn more about the [dev command](../providers/aws/cli-reference/dev.md).
 
 ```bash
 serverless dev