summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAlbin Vass <albin.vass@volvocars.com>2020-03-09 14:56:18 +0100
committerAlbin Vass <albin.vass@volvocars.com>2020-03-09 14:56:28 +0100
commited9eb45d33ad06c3e0b9ea3a849978834fa50541 (patch)
tree9aaf01734a90cdc0b3db9db8b5172e483e061144 /doc
parent2881ee578599b199280c60fb76b5201dd855f419 (diff)
downloadzuul-ed9eb45d33ad06c3e0b9ea3a849978834fa50541.tar.gz
Fix minor spelling error
Change-Id: Iebedeba265780c211df618b2f30e96c79b893864
Diffstat (limited to 'doc')
-rw-r--r--doc/source/reference/developer/specs/scale-out-scheduler.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/reference/developer/specs/scale-out-scheduler.rst b/doc/source/reference/developer/specs/scale-out-scheduler.rst
index 4fd774863..ed43ea47c 100644
--- a/doc/source/reference/developer/specs/scale-out-scheduler.rst
+++ b/doc/source/reference/developer/specs/scale-out-scheduler.rst
@@ -226,7 +226,7 @@ In order to prepare for distributed pipeline execution we need to use Zookeeper
for scheduling jobs on the executors. This is needed so that any scheduler can
take over a pipeline execution without having to restart jobs.
-As discribed above the executor will look for builds. These will be stored in
+As described above the executor will look for builds. These will be stored in
``/zuul/builds/<sequence>``. The builds will contain every information that is
needed to run the job. The builds are stored outside of the pipeline itself
for two reasons. First the executors should not need to do a deep search when