From 03a038f813459eafd870b1b3953cfc9f8f8d1a57 Mon Sep 17 00:00:00 2001 From: Lian Li Date: Fri, 8 Jul 2022 18:33:54 +0200 Subject: [PATCH] fixes small typo --- docs/pages/configuration/imports/README.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/configuration/imports/README.mdx b/docs/pages/configuration/imports/README.mdx index 7830b9b3dc..218ce6fa3b 100644 --- a/docs/pages/configuration/imports/README.mdx +++ b/docs/pages/configuration/imports/README.mdx @@ -50,7 +50,7 @@ The following table clarifies when to use `imports` and when to use `dependencie | Difference | `imports` | `dependencies` | | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Use Case | Importing shared/standardized functionality (e.g. `functions`, `pipelines`, `commands`) into **independent** projects | Defining logical dependencies between **inter-dependent** projects (app A requiring app B to be deployed) | -| Example | If projects A and B should both have some shared functionality that is defined in a shared `devspace.yaml` | If a project A with requires projectd B and C to be deployed in order to work correctly | +| Example | If projects A and B should both have some shared functionality that is defined in a shared `devspace.yaml` | If a project A with requires projects B and C to be deployed in order to work correctly | | Impact | If project A imports a `devspace.yaml` from another `devspace.yaml`, then everything defined in this imported `devspace.yaml` will be merged into the `devspace.yaml` of project A. | If project A has a `devspace.yaml` that defines project B as a git-based `dependency`, then DevSpace will `git clone` project B and deploy it when you run `run_dependency_pipelines b` inside your pipeline script. |