From ed9eb45d33ad06c3e0b9ea3a849978834fa50541 Mon Sep 17 00:00:00 2001 From: Albin Vass Date: Mon, 9 Mar 2020 14:56:18 +0100 Subject: [PATCH] Fix minor spelling error Change-Id: Iebedeba265780c211df618b2f30e96c79b893864 --- doc/source/reference/developer/specs/scale-out-scheduler.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/reference/developer/specs/scale-out-scheduler.rst b/doc/source/reference/developer/specs/scale-out-scheduler.rst index 4fd7748631..ed43ea47ce 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/``. 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