Update docs [ci skip]

Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
nextflow-io · Oct 23, 2024 · 3f6f377 · 3f6f377
1 parent 17b7ab5
commit 3f6f377
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 4 deletions.
diff --git a/docs/script.md b/docs/script.md
@@ -382,8 +382,6 @@ When a closure takes a single parameter, the parameter can be omitted, in which
 ```groovy
 [1, 2, 3].each { println it }
 ```
-
-However, this practice is deprecated and will not be supported in the future.
 :::
 
 ## Script definitions

diff --git a/docs/workflow.md b/docs/workflow.md
@@ -51,7 +51,7 @@ workflow {
 ```
 
 :::{note}
-While params can also be used by named workflows, this practice is deprecated and will not be supported in the future. Named workflows should receive their inputs explicitly through the `take:` section.
+While params can also be used by named workflows, this practice is discouraged. Named workflows should receive their inputs explicitly through the `take:` section.
 :::
 
 ## Workflow inputs (`take`)
@@ -234,7 +234,7 @@ Process named outputs are defined using the `emit` option on a process output. S
 :::
 
 :::{note}
-Process and workflow outputs can also be accessed by index (e.g., `foo.out[0]`, `foo.out[1]`, etc.). However, this practice is deprecated and will not be supported in the future. Multiple outputs should instead be accessed by name.
+Process and workflow outputs can also be accessed by index (e.g., `foo.out[0]`, `foo.out[1]`, etc.). Multiple outputs should instead be accessed by name.
 :::
 
 Workflows can be composed in the same way: