From 126b0ce7e72145d4636152a8f24b86f1fc9a0d73 Mon Sep 17 00:00:00 2001 From: Kunal Pathak Date: Sat, 15 Mar 2025 13:15:40 +0100 Subject: [PATCH] Grammar fixes to local-development.mdx --- docs/documentation/guides/local-development.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/guides/local-development.mdx b/docs/documentation/guides/local-development.mdx index 6d606bafe..2d4c21567 100644 --- a/docs/documentation/guides/local-development.mdx +++ b/docs/documentation/guides/local-development.mdx @@ -6,7 +6,7 @@ description: "Learn how to manage secrets in local development environments." ## Problem at hand -There is a number of issues that arise with secret management in local development environment: +There are a number of issues that arise with secret management in local development environment: 1. **Getting secrets onto local machines**. When new developers join or a new project is created, the process of getting the development set of secrets onto local machines is often unclear. As a result, developers end up spending a lot of time onboarding and risk potentially following insecure practices when sharing secrets from one developer to another. 2. **Syncing secrets with teammates**. One of the problems with .env files is that they become unsynced when one of the developers updates a secret or configuration. Even if the rest of the team is notified, developers don't make all the right changes immediately, and later on end up spending a lot of time debugging an issue due to missing environment variables. This leads to a lot of inefficiencies and lost time. 3. **Accidentally leaking secrets**. When developing locally, it's common for developers to accidentally leak a hardcoded secret as part of a commit. As soon as the secret is part of the git history, it becomes hard to get it removed and create a security vulnerability.