doc/tutorials/basics: remove duplicate text
Closes #263.
Change-Id: Ic3738ed25fe0b85547ef05d3e2b67ee307b05978
Reviewed-on: https://cue-review.googlesource.com/c/cue/+/4665
Reviewed-by: Marcel van Lohuizen <mpvl@golang.org>
diff --git a/doc/tutorial/basics/0_intro/40_constraints.txt b/doc/tutorial/basics/0_intro/40_constraints.txt
index 363edaf..80fc450 100644
--- a/doc/tutorial/basics/0_intro/40_constraints.txt
+++ b/doc/tutorial/basics/0_intro/40_constraints.txt
@@ -11,9 +11,6 @@
but conceptually they can be explained as something in between types and
concrete values.
-Constraints can be used to validate values of concrete instances.
-They can be applied to CUE data, or directly to YAML or JSON.
-
But constraints can also reduce boilerplate.
If a constraint defines a concrete value, there is no need
to specify it in values to which this constraint applies.
diff --git a/doc/tutorial/basics/0_intro/47_validation.txt b/doc/tutorial/basics/0_intro/47_validation.txt
index 95ccb49..f2a89a2 100644
--- a/doc/tutorial/basics/0_intro/47_validation.txt
+++ b/doc/tutorial/basics/0_intro/47_validation.txt
@@ -6,18 +6,9 @@
description = ""
-- text.md --
-Constraints specify what values are allowed.
-To CUE they are just values like anything else,
-but conceptually they can be explained as something in between types and
-concrete values.
-
Constraints can be used to validate values of concrete instances.
They can be applied to CUE data, or directly to YAML or JSON.
-But constraints can also reduce boilerplate.
-If a constraint defines a concrete value, there is no need
-to specify it in values to which this constraint applies.
-
-- schema.cue --
Language :: {
tag: string
