doc/ref: fix three mistakes in the matchIf examples
The second and third examples used four arguments instead of three;
the label on the left side of the field declaration was repeated
as the first argument, almost like it was a receiver parameter.
The second example was also not behaving as documented,
because the line after the fix above would still succeed `cue export`.
This is because `b` was not actually a required field,
so `{a: 1} & {a: int, b: int}` succeeds and passes the validation.
Make the `b` field required to match the intented behavior in the docs.
Finally, the results of these unifications are not booleans;
rather than noting each of the expected outcomes as `true` or `false`,
use the words "OK" or "error", and consistently say why.
Signed-off-by: Daniel Martí <mvdan@mvdan.cc>
Change-Id: I0d34509a20cecfe527215e44cb5542d96fc9dacc
Reviewed-on: https://cue.gerrithub.io/c/cue-lang/cue/+/1232059
Unity-Result: CUE porcuepine <cue.porcuepine@gmail.com>
TryBot-Result: CUEcueckoo <cueckoo@cuelang.org>
Reviewed-by: Marcel van Lohuizen <mpvl@gmail.com>