From a462a9f488029237d57773945e1adb9fae2ab6a8 Mon Sep 17 00:00:00 2001 From: Andrei Rybak Date: Tue, 2 Nov 2021 14:39:58 +0100 Subject: [PATCH] docs: fix typos Fix various typos in Markdown documentation files. --- README.md | 8 ++++---- doc/manual/src/hacking.md | 2 +- doc/manual/src/notifications.md | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index e1c2725c..50e7ba6d 100644 --- a/README.md +++ b/README.md @@ -31,13 +31,13 @@ $ hydra-create-user --full-name '' \ --email-address '' --password --role admin ``` -Afterwards you should be able to log by clicking on "_Sign In_" on the top right of the web interface using the credentials specified by `hydra-crate-user`. Once you are logged in you can click "_Admin -> Create Project_" to configure your first project. +Afterwards you should be able to log by clicking on "_Sign In_" on the top right of the web interface using the credentials specified by `hydra-create-user`. Once you are logged in you can click "_Admin -> Create Project_" to configure your first project. ### Creating A Simple Project And Jobset -In order to evaluate and build anything you need to crate _projects_ that contain _jobsets_. Hydra supports imperative and declarative projects and many different configurations. The steps below will guide you through the required steps to creating a minimal imperative project configuration. +In order to evaluate and build anything you need to create _projects_ that contain _jobsets_. Hydra supports imperative and declarative projects and many different configurations. The steps below will guide you through the required steps to creating a minimal imperative project configuration. #### Creating A Project -Log in as adminstrator, click "_Admin_" and select "_Create project_". Fill the form as follows: +Log in as administrator, click "_Admin_" and select "_Create project_". Fill the form as follows: - **Identifier**: `hello` - **Display name**: `hello` @@ -53,7 +53,7 @@ After creating a project you are forwarded to the project page. Click "_Actions_ - **Check interval**: 60 - **Scheduling shares**: 1 -We have to add two inputs for this jobset. One for _nixpkgs_ and one for _hydra_ (which we are referrencing in the Nix expression above): +We have to add two inputs for this jobset. One for _nixpkgs_ and one for _hydra_ (which we are referencing in the Nix expression above): - **Input name**: `nixpkgs` - **Type**: `Git checkout` diff --git a/doc/manual/src/hacking.md b/doc/manual/src/hacking.md index 2ed00bd6..9d98b00c 100644 --- a/doc/manual/src/hacking.md +++ b/doc/manual/src/hacking.md @@ -74,7 +74,7 @@ $ nix-build release.nix -A build.x86_64-linux ### Connecting to the database -Assuming you're running the the default configuration with `foreman start`, +Assuming you're running the default configuration with `foreman start`, open an interactive session with Postgres via: ```console diff --git a/doc/manual/src/notifications.md b/doc/manual/src/notifications.md index fc41f7ea..b8f24580 100644 --- a/doc/manual/src/notifications.md +++ b/doc/manual/src/notifications.md @@ -11,7 +11,7 @@ Note that the notification format is subject to change and should not be conside ### `build_started` * **Payload:** Exactly one value, the ID of the build. -* **When:** Issued directly before building happens, and only if the derivation's outputs cannot be subsituted. +* **When:** Issued directly before building happens, and only if the derivation's outputs cannot be substituted. * **Delivery Semantics:** Ephemeral. `hydra-notify` must be running to react to this event. No record of this event is stored. ### `step_finished`