crihook: update documentation

Author: bart0sh

cmd/fpga_crihook/README.md

@@ -8,20 +8,19 @@ Table of Contents
 
 ## Introduction
 
-The FPGA CRI-O webhook is one of the components used to add support for Intel FPGA
+The FPGA CDI hook is one of the components used to add support for Intel FPGA
 devices to Kubernetes.
 
-The FPGA prestart CRI-O hook is triggered by container annotations, such as set by the
-[FPGA device plugin](../fpga_plugin/README.md).  It performs discovery of the requested FPGA
-function bitstream and then programs FPGA devices based on the environment variables
-in the workload description.
+The FPGA prestart hook is passed by the [FPGA device plugin](../fpga_plugin/README.md) as
+a CDI device attribute to the Kubelet and then to the CRI runtime.
+It performs discovery of the requested FPGA function bitstream and then programs FPGA devices
+based on the environment variables in the workload description.
 
-The CRI-O prestart hook is only *required* when the
-[FPGA admission webhook](../fpga_admissionwebhook/README.md) is configured for orchestration
-programmed mode, and is benign (un-used) otherwise.
+The hook is only *required* when the [FPGA admission webhook](../fpga_admissionwebhook/README.md)
+is configured for orchestration programmed mode, and is benign (un-used) otherwise.
 
-> **Note:** The fpga CRI-O webhook is usually installed by the same DaemonSet as the
-> FPGA device plugin. If building and installing the CRI-O webhook by hand, it is
+> **Note:** The fpga CDI hook is usually installed by the same DaemonSet as the
+> FPGA device plugin. If building and installing the hook by hand, it is
 > recommended you reference the
 > [fpga plugin DaemonSet YAML](/deployments/fpga_plugin/base/intel-fpga-plugin-daemonset.yaml ) for
 > more details.
@@ -39,11 +38,8 @@ All components have the same basic dependencies as the
 
 See [the development guide](../../DEVEL.md) for details if you want to deploy a customized version of the CRI hook.
 
-## Configuring CRI-O
+## Configuring CRI runtimes
 
-Recent versions of [CRI-O](https://github.com/cri-o/cri-o) are shipped with default configuration
-file that prevents CRI-O to discover and configure hooks automatically.
-For FPGA orchestration programmed mode, the OCI hooks are the key component.
-Please ensure that your `/etc/crio/crio.conf` parameter `hooks_dir` is either unset
-(to enable default search paths for OCI hooks configuration) or contains the directory
-`/etc/containers/oci/hooks.d`.
+CDI should be enabled for the CRI runtime to call the hook. CRI-O has it enabled by
+default and for Containerd it should be enabled explicitly in its configuration file as
+explained in the [CDI documentation](https://github.com/cncf-tags/container-device-interface?tab=readme-ov-file#how-to-configure-cdi)