Fixed bad URL (#2333)

doc/Type/Signature.pod6

@@ -395,18 +395,18 @@ be confusing, since the terms have subtly different meanings.
 
 As explained above, I<definiteness> is concerned with the distinction between
 type objects and object instances. A type object is always indefinite, while an
-object instance is always definite. Whether or not an object is a type
+object instance is always definite. Whether an object is a type
 object/indefinite or an object instance/definite can be verified using the
 L<DEFINITE|/language/mop#DEFINITE> (meta)method.
 
 I<Definiteness> should be distinghuished from I<definedness>, which is concerned
 with the difference between defined and undefined objects. Whether an object is
-defined or undefined can be verified using the C<.defined>-method, which is
+defined or undefined can be verified using the C<defined>-method, which is
 implemented in class L<Mu|/type/Mu>. By default a type object is considered
 undefined, while an object instance is considered defined; that is: C<.defined>
 returns C<False> on a type object, and C<True> otherwise. But this default
 behaviour may be overridden by subclasses. An example of a subclass that
-overrides the default C<.defined> behaviour is L<Failure|type/Failure>,
+overrides the default C<.defined> behaviour is L<Failure|/type/Failure>,
 so that even an instantiated C<Failure> acts as an undefined value:
 
     my $a = Failure;                # Initialize with type object