referencing, not Bowtie

Author: Julian

docs/compatibility.rst

@@ -10,7 +10,7 @@ Once it seems clear that the interfaces look correct (likely after ``referencing
     Backwards compatibility is always defined relative to the specifications we implement.
     Changing a behavior which is incorrect according to the relevant referencing specifications is not considered a backwards-incompatible change -- on the contrary, it's considered a bug fix.
 
-In the spirit of `having some explicit detail on Bowtie's public interfaces <regret:before-you-deprecate:document your public api>`, here is a non-exhaustive list of things which are *not* part of the ``referencing`` public interface, and therefore which may change without warning, even once no longer in beta:
+In the spirit of `having some explicit detail on referencing's public interfaces <regret:before-you-deprecate:document your public api>`, here is a non-exhaustive list of things which are *not* part of the ``referencing`` public interface, and therefore which may change without warning, even once no longer in beta:
 
 * All commonly understood indicators of privacy in Python -- in particular, (sub)packages, modules and identifiers beginning with a single underscore.
   In the case of modules or packages, this includes *all* of their contents recursively, regardless of their naming.