diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md index 6b6aa64a3..4bbe0e2ad 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -8,7 +8,7 @@ assignees: '' --- ### Feature description -A clear and concise description of what the the feature should be. +A clear and concise description of what the feature should be. ### Why would it be useful? Why would this feature be useful for Infisical users? diff --git a/docs/documentation/getting-started/docker.mdx b/docs/documentation/getting-started/docker.mdx index 567745ea4..4a3c79ee8 100644 --- a/docs/documentation/getting-started/docker.mdx +++ b/docs/documentation/getting-started/docker.mdx @@ -15,7 +15,7 @@ Prerequisites: ## Dockerfile Modification - Follow the instruction for your specific Linux distrubtion to add the Infisical CLI to your Dockerfile. + Follow the instructions for your specific Linux distribution to add the Infisical CLI to your Dockerfile. @@ -87,7 +87,7 @@ Prerequisites: ## Dockerfile Modifications - Follow the instruction for your specific Linux distributions to add the Infisical CLI to your Dockerfiles. + Follow the instructions for your specific Linux distributions to add the Infisical CLI to your Dockerfiles. @@ -182,4 +182,4 @@ Prerequisites: See also: - [Documentation for Docker](/integrations/platforms/docker) -- [Documentation for Docker Compose](/integrations/platforms/docker-compose) \ No newline at end of file +- [Documentation for Docker Compose](/integrations/platforms/docker-compose) diff --git a/docs/documentation/guides/node.mdx b/docs/documentation/guides/node.mdx index 323d95072..d182840b4 100644 --- a/docs/documentation/guides/node.mdx +++ b/docs/documentation/guides/node.mdx @@ -28,7 +28,7 @@ Now that we've created a project and added a secret to its development environme ## Create a Node app -For this demonstration, we use a minimal Express application. However, the same principles will apply for any Node application such as those built on Koa or Fastify. +For this demonstration, we use a minimal Express application. However, the same principles will apply to any Node application such as those built on Koa or Fastify. ### Create an Express app @@ -107,7 +107,7 @@ At this stage, you know how to fetch secrets from Infisical back to your Node ap Although the SDK requires you to pass in a token, it enables greater efficiency and security than if you managed dozens of secrets yourself without it. Here're some benefits: - - You always pull in the right secrets because they're fetched on demand from a centralize source that is Infisical. + - You always pull in the right secrets because they're fetched on demand from a centralized source that is Infisical. - You can use the Infisical which comes with tons of benefits like secret versioning, access controls, audit logs, etc. - You now risk leaking one token that can be revoked instead of dozens of raw secrets. @@ -118,4 +118,4 @@ At this stage, you know how to fetch secrets from Infisical back to your Node ap See also: -- Explore the [Node SDK](https://github.com/Infisical/infisical-node) \ No newline at end of file +- Explore the [Node SDK](https://github.com/Infisical/infisical-node) diff --git a/docs/documentation/guides/python.mdx b/docs/documentation/guides/python.mdx index 2c558a69c..50ee44a86 100644 --- a/docs/documentation/guides/python.mdx +++ b/docs/documentation/guides/python.mdx @@ -27,7 +27,7 @@ Now that we've created a project and added a secret to its development environme ## Create a Python app -For this demonstration, we use a minimal Flask application. However, the same principles will apply for any Python application such as those built with Django. +For this demonstration, we use a minimal Flask application. However, the same principles will apply to any Python application such as those built with Django. ### Create a Flask app @@ -103,7 +103,7 @@ At this stage, you know how to fetch secrets from Infisical back to your Python Although the SDK requires you to pass in a token, it enables greater efficiency and security than if you managed dozens of secrets yourself without it. Here're some benefits: - - You always pull in the right secrets because they're fetched on demand from a centralize source that is Infisical. + - You always pull in the right secrets because they're fetched on demand from a centralized source that is Infisical. - You can use the Infisical which comes with tons of benefits like secret versioning, access controls, audit logs, etc. - You now risk leaking one token that can be revoked instead of dozens of raw secrets. diff --git a/docs/documentation/platform/folder.mdx b/docs/documentation/platform/folder.mdx index b112b5787..506b30da2 100644 --- a/docs/documentation/platform/folder.mdx +++ b/docs/documentation/platform/folder.mdx @@ -4,7 +4,7 @@ description: "Organize your secrets with folders" --- Folders provide a powerful and intuitive way to structure your secrets. -They offer a system to keep your secrets organized and easily accessible, which becomes increasingly important as your collection of secrets grow. +They offer a system to keep your secrets organized and easily accessible, which becomes increasingly important as your collection of secrets grows. With folders in Infisical, you can now create a hierarchy of folders to organize your secrets, mirroring your application's architecture or any logical grouping that suits your needs. Whether you follow a microservices architecture or work with monorepos, folders make it simpler to locate, manage and collaborate between teams.