Remove internal crate links from readme

Author: phil-opp

README.md

@@ -4,10 +4,10 @@
 
 Provides volatile wrapper types for raw pointers.
 
-The volatile wrapper types in this crate wrap a pointer to any [`Copy`]-able type and provide volatile memory access to wrapped value.
+The volatile wrapper types in this crate wrap a pointer to any `Copy`-able type and provide volatile memory access to wrapped value.
 Volatile memory accesses are never optimized away by the compiler, and are useful in many low-level systems programming and concurrent contexts.
 
-This crate provides two different wrapper types: [`VolatilePtr`] and [`VolatileRef`].
+This crate provides two different wrapper types: `VolatilePtr` and `VolatileRef`.
 The difference between the two types is that the former behaves like a raw pointer, while the latter behaves like a Rust reference type.
 For example, `VolatilePtr` can be freely copied, but not sent across threads because this could introduce mutable aliasing.
 The `VolatileRef` type, on the other hand, requires exclusive access for mutation, so that sharing it across thread boundaries is safe.
@@ -17,7 +17,7 @@ Both wrapper types *do not* enforce any atomicity guarantees; to also get atomic
 ## Why is there no `VolatileCell`?
 
 Many people expressed interest in a `VolatileCell` type, i.e. a transparent wrapper type that owns the wrapped value.
-Such a type would be similar to [`core::cell::Cell`], with the difference that all methods are volatile.
+Such a type would be similar to `core::cell::Cell`, with the difference that all methods are volatile.
 Unfortunately, it is not sound to implement such a `VolatileCell` type in Rust.
 The reason is that Rust and LLVM consider `&` and `&mut` references as _dereferencable_.
 This means that the compiler is allowed to freely access the referenced value without any restrictions.