B OpenNebula/one#3189: Update patch procedure

source/deployment/open_cloud_host_setup/lxd_driver.rst

@@ -262,7 +262,7 @@ Troubleshooting
 ==================
 - The oneadmin user has his ``$HOME`` in a non ``/home/$USER`` location. This prevents the oneadmin account from properly using the LXD CLI due to a snap limitation. You can use sudo to use other account to run lxd commands.
 - The command parameter in the VNC configuration dictates which command will appear in noVNC when entering a container. Having ``/bin/bash`` will skip the user login and gain root access on the container.
-- If you experience `reboot issues <https://github.com/OpenNebula/one/issues/3189>`_ you can apply a network hook patch by making executable the file ``chmod +x /var/lib/one/remotes/vnm/<net_driver>/clean.d/lxd_clean.rb`` and issuing ``onehost sync --force``. This have to be done for all network drivers used in your cloud.
+- If you experience `reboot issues <https://github.com/OpenNebula/one/issues/3189>`_ you can apply a network hook patch by copying the file ``/usr/share/one/examples/network_hooks/99-lxd_clean.rb`` to ``/var/lib/one/remotes/vnm/<network_driver>/clean.d`` and issuing ``onehost sync --force``. This have to be done for all network drivers used in your cloud.
 
 .. TODO Review with latest format, include a simple mapper