overview: Use CRI for the interface, not CRI-O

CRI-O is a specific implementation of the Kubernetes Container
Runtime Interface (CRI), so when talking about the interface point
to the latter.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

content/concepts/overview.md

@@ -230,7 +230,8 @@ advantage of common workflows developers are used to for building images
 targeting cloud deployments.
 
 The other benefit of using OCI standards is the potential to use/consider
-different [CRI-O](https://cri-o.io/) implementation, including implementations
+different [CRI](https://kubernetes.io/docs/concepts/architecture/cri/)
+implementations, including implementations
 using hypervisor technology to allow for an even bigger separation of host and
 container then typically available on namespace based container systems.