diff --git a/apps/web/.env.example b/apps/web/.env.example
index 63716f63..db2e770a 100644
--- a/apps/web/.env.example
+++ b/apps/web/.env.example
@@ -28,7 +28,7 @@ JWT_SECRET='secret'
 PLAYWRIGHT_SECRET=
 
 # To enable SAML login, set both these variables
-# @see https://github.com/calendso/calendso/tree/main/ee#setting-up-saml-login
+# @see https://github.com/calcom/cal.com/tree/main/packages/ee#setting-up-saml-login
 # SAML_DATABASE_URL="postgresql://postgres:@localhost:5450/cal-saml"
 # SAML_ADMINS='pro@example.com'
 # If you use Heroku to deploy Postgres (or use self-signed certs for Postgres) then uncomment the follow line.
diff --git a/apps/web/docs/saml-setup.md b/apps/web/docs/saml-setup.md
index 29792aec..aaf55207 100644
--- a/apps/web/docs/saml-setup.md
+++ b/apps/web/docs/saml-setup.md
@@ -1,6 +1,6 @@
 # SAML Registration with Identity Providers
 
-This guide explains the settings you’d need to use to configure SAML with your Identity Provider. Once this is set up you should get an XML metadata file that should then be uploaded on your Cal.com self-hosted instance.
+This guide explains the settings you need to use to configure SAML with your Identity Provider. Once this is set up you should get an XML metadata file that should then be uploaded on your Cal.com self-hosted instance.
 
 > **Note:** Please do not add a trailing slash at the end of the URLs. Create them exactly as shown below.
 
diff --git a/packages/ee/README.md b/packages/ee/README.md
index d5af7e20..d73b8b86 100644
--- a/packages/ee/README.md
+++ b/packages/ee/README.md
@@ -30,7 +30,7 @@ The [/ee](https://github.com/calcom/cal.com/tree/main/apps/web/ee) subfolder is
 
 1. Set SAML_DATABASE_URL to a postgres database. Please use a different database than the main Cal instance since the migrations are separate for this database. For example `postgresql://postgres:@localhost:5450/cal-saml`
 2. Set SAML_ADMINS to a comma separated list of admin emails from where the SAML metadata can be uploaded and configured.
-3. Create a SAML application with your Identity Provider (IdP) using the instructions here - [SAML Setup](../docs/saml-setup.md)
+3. Create a SAML application with your Identity Provider (IdP) using the instructions here - [SAML Setup](../../apps/web/docs/saml-setup.md)
 4. Remember to configure access to the IdP SAML app for all your users (who need access to Cal).
 5. You will need the XML metadata from your IdP later, so keep it accessible.
 6. Log in to one of the admin accounts configured in SAML_ADMINS and then navigate to Settings -> Security.
diff --git a/packages/stripe/README.md b/packages/stripe/README.md
index d5af7e20..d73b8b86 100644
--- a/packages/stripe/README.md
+++ b/packages/stripe/README.md
@@ -30,7 +30,7 @@ The [/ee](https://github.com/calcom/cal.com/tree/main/apps/web/ee) subfolder is
 
 1. Set SAML_DATABASE_URL to a postgres database. Please use a different database than the main Cal instance since the migrations are separate for this database. For example `postgresql://postgres:@localhost:5450/cal-saml`
 2. Set SAML_ADMINS to a comma separated list of admin emails from where the SAML metadata can be uploaded and configured.
-3. Create a SAML application with your Identity Provider (IdP) using the instructions here - [SAML Setup](../docs/saml-setup.md)
+3. Create a SAML application with your Identity Provider (IdP) using the instructions here - [SAML Setup](../../apps/web/docs/saml-setup.md)
 4. Remember to configure access to the IdP SAML app for all your users (who need access to Cal).
 5. You will need the XML metadata from your IdP later, so keep it accessible.
 6. Log in to one of the admin accounts configured in SAML_ADMINS and then navigate to Settings -> Security.