diff --git a/docs/updating-syntax.md b/docs/updating-syntax.md
index 10b48e8033..ede255b773 100644
--- a/docs/updating-syntax.md
+++ b/docs/updating-syntax.md
@@ -550,6 +550,6 @@ There are two ways to preserve Groovy code:
  - Move the code to the `lib` directory
  - Create a plugin
 
-Any Groovy code can be moved into the `lib` directory, which supports the full Groovy language. This approach is useful for temporarily preserving some Groovy code until it can be updated later and incorporated into a Nextflow script. See {ref}`<lib-directory>` documentation for more information.
+Any Groovy code can be moved into the `lib` directory, which supports the full Groovy language. This approach is useful for temporarily preserving some Groovy code until it can be updated later and incorporated into a Nextflow script. See {ref}`lib-directory` documentation for more information.
 
 For Groovy code that is complicated or if it depends on third-party libraries, it may be better to create a plugin. Plugins can define custom functions that can be included by Nextflow scripts like a module. Furthermore, plugins can be easily re-used across different pipelines. See {ref}`plugins-dev-page` for more information on how to develop plugins.