Minor rephrasing and example compilation fixing

doc/Type/Junction.pod6

@@ -60,15 +60,17 @@ Note that the compiler is allowed, but not required, to parallelize
 autothreading (and Junction behavior in general), so it is usually an
 error to autothread junctions over code with side effects.
 
-It is possible I<future language versions> will include short-circuiting
+It is possible that I<future language versions> will include short-circuiting
 behaviour in Junctions. For example one or more routine calls (C<a()>, C<b()>,
 or C<c()>) in the code below might not get executed at all, if the result of
 the conditional has been fully determined from routine calls already performed
-(only one truthy return value is required to know the entire Junction is true):
+(only one truthy return value is enough to know the entire Junction is true):
 
-    if a() | b() | c() {
-        say "At least one of the routines was called and returned a truthy value"
-    }
+=begin code :preamble<sub a(){}; sub b(){}; sub c(){}>
+if a() | b() | c() {
+    say "At least one of the routines was called and returned a truthy value"
+}
+=end code
 
 Junctions are meant to be used as matchers in boolean context; introspection
 of junctions is not supported. If you feel the urge to introspect a junction,