| commit | 7739e724a2a9754f90197f2b9ec4f6d9fc72897c | [log] [tgz] |
|---|---|---|
| author | Marcel van Lohuizen <mpvl@golang.org> | Thu Jan 16 12:32:55 2020 +0100 |
| committer | Marcel van Lohuizen <mpvl@golang.org> | Thu Jan 16 12:23:22 2020 +0000 |
| tree | 9e09a105ead858ed58ef831f5b0284c5ea83e382 | |
| parent | 6cb0878a1ef86cd2e63dc3bd31f32811ecf69730 [diff] |
doc/tutorials/basics: typo Closes #263 Change-Id: I70fe6b0982a8890100195cbd0f31138560667a15 Reviewed-on: https://cue-review.googlesource.com/c/cue/+/4663 Reviewed-by: Marcel van Lohuizen <mpvl@golang.org>
diff --git a/doc/tutorial/basics/0_intro/47_validation.txt b/doc/tutorial/basics/0_intro/47_validation.txt index 0f3c4fe..95ccb49 100644 --- a/doc/tutorial/basics/0_intro/47_validation.txt +++ b/doc/tutorial/basics/0_intro/47_validation.txt
@@ -15,7 +15,7 @@ They can be applied to CUE data, or directly to YAML or JSON. But constraints can also reduce boilerplate. -If a constraints defines a concrete value, there is no need +If a constraint defines a concrete value, there is no need to specify it in values to which this constraint applies. -- schema.cue --