From 5bd8fc9ae49d2a638c3cbdb994052260342b8ef0 Mon Sep 17 00:00:00 2001
From: Victor Santos <victor@infisical.com>
Date: Mon, 24 Nov 2025 20:23:30 -0300
Subject: [PATCH] fix: correct minor typos in GitLab and AWS Amplify
 documentation

---
 docs/integrations/app-connections/gitlab.mdx | 2 +-
 docs/integrations/cicd/aws-amplify.mdx       | 2 +-
 docs/integrations/secret-syncs/overview.mdx  | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/integrations/app-connections/gitlab.mdx b/docs/integrations/app-connections/gitlab.mdx
index d17322540..588a6f990 100644
--- a/docs/integrations/app-connections/gitlab.mdx
+++ b/docs/integrations/app-connections/gitlab.mdx
@@ -12,7 +12,7 @@ Infisical supports two methods for connecting to GitLab: **OAuth** and **Access
     <Accordion title="Self-Hosted Instance Setup">
       Using the GitLab Connection with OAuth on a self-hosted instance of Infisical requires configuring an OAuth application in GitLab and registering your instance with it.
 
-      <Tip>If you're self-hosting Gitlab with custom certificates, you will have to configure your Infisical instance to trust these certificates. To learn how, please follow [this guide](../../self-hosting/guides/custom-certificates).</Tip>
+      <Tip>If you're self-hosting GitLab with custom certificates, you will have to configure your Infisical instance to trust these certificates. To learn how, please follow [this guide](../../self-hosting/guides/custom-certificates).</Tip>
 
       **Prerequisites:**
       - A GitLab account with existing projects
diff --git a/docs/integrations/cicd/aws-amplify.mdx b/docs/integrations/cicd/aws-amplify.mdx
index 9b4b81ccb..28de7640c 100644
--- a/docs/integrations/cicd/aws-amplify.mdx
+++ b/docs/integrations/cicd/aws-amplify.mdx
@@ -19,7 +19,7 @@ This approach enables you to fetch secrets from Infisical during Amplify build t
   <Tab title="Machine Identity (Recommended)">
     <Steps>
       <Step title="Create a machine identity">
-          Create a machine identtiy and connect it to your Infisical project. You can read more about how to use machine identities [here](/documentation/platform/identities/machine-identities). The machine identity will allow you to authenticate and fetch secrets from Infisical.
+          Create a machine identity and connect it to your Infisical project. You can read more about how to use machine identities [here](/documentation/platform/identities/machine-identities). The machine identity will allow you to authenticate and fetch secrets from Infisical.
       </Step>
 
       <Step title="Set the machine identity client ID and client secret as Amplify environment variables">
diff --git a/docs/integrations/secret-syncs/overview.mdx b/docs/integrations/secret-syncs/overview.mdx
index eeadcffa3..c341e6ea3 100644
--- a/docs/integrations/secret-syncs/overview.mdx
+++ b/docs/integrations/secret-syncs/overview.mdx
@@ -88,7 +88,7 @@ via the UI or API for the third-party service you intend to sync secrets to.
 
 <Note>
     Infisical is continuously expanding it's Secret Sync third-party service support. If the service you need isn't available,
-    you can contact us at team@infisical.com to make a request .
+    you can contact us at team@infisical.com to make a request.
 </Note>
 
 ## Key Schemas