From 9feb6be9f27578de9ed7dbdcb0ed138e4fef1f12 Mon Sep 17 00:00:00 2001
From: FestplattenSchnitzel
 <45077355+FestplattenSchnitzel@users.noreply.github.com>
Date: Sun, 23 Jan 2022 02:25:44 +0100
Subject: [PATCH] Fix typo (#714)

---
 docs/docs/20-usage/25-multi-pipeline.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/20-usage/25-multi-pipeline.md b/docs/docs/20-usage/25-multi-pipeline.md
index 1fb4cc55d..d798301d8 100644
--- a/docs/docs/20-usage/25-multi-pipeline.md
+++ b/docs/docs/20-usage/25-multi-pipeline.md
@@ -16,7 +16,7 @@ The Multi-Pipeline feature allows the pipeline to be split into several files an
 
 ## Example multi-pipeline definition
 :::warning
-Please note that files are only shared bewteen steps of the same pipeline (see [File changes are incremental](/docs/usage/pipeline-syntax#file-changes-are-incremental)). That means you cannot access artifacts e.g. from the `build` pipeline below in the `deploy` pipeline.
+Please note that files are only shared between steps of the same pipeline (see [File changes are incremental](/docs/usage/pipeline-syntax#file-changes-are-incremental)). That means you cannot access artifacts e.g. from the `build` pipeline below in the `deploy` pipeline.
 If you still need to pass artifacts between the pipelines you need use storage [plugins](docs/usage/plugins/plugins) (e.g. one which stores files in an Amazon S3 bucket).
 :::