Apply suggestions from code review

Co-authored-by: Chris Hakkaart <[email protected]>
Signed-off-by: Ben Sherman <[email protected]>

Author: bentsherman

docs/migrations/25-04.md

@@ -62,7 +62,7 @@ workflow {
 }
 ```
 
-This syntax allows you to declare all parameters in one place, and allows Nextflow to validate parameters at runtime.
+This syntax allows you to declare all parameters in one place and allows Nextflow to validate them at runtime.
 
 See {ref}`workflow-params-def` for details.
 

docs/vscode.md

@@ -26,7 +26,7 @@ The language server parses scripts and config files according to the {ref}`Nextf
 
 When you hover over certain source code elements, such as variable names and function calls, the extension provides a tooltip with related information, such as the definition and/or documentation for the element.
 
-If a [Javadoc](https://en.wikipedia.org/wiki/Javadoc) comment is defined above a workflow, process, function, type definition, or parameter in a `params` block, the extension will include the contents of the comment in hover hints. Here is an example Javadoc comment:
+If a [Javadoc](https://en.wikipedia.org/wiki/Javadoc) comment is defined above a workflow, process, function, type definition, or parameter in a `params` block, the extension will include the contents of the comment in hover hints. The following is an example Javadoc comment:
 
 ```nextflow
 /**

docs/workflow.md

@@ -26,7 +26,7 @@ workflow {
 
 ## Parameters
 
-There are two ways to declare parameters in a Nextflow script: the `params` block and *legacy* parameters.
+Parameters can be declared in a Nextflow script with the `params` block or with *legacy* parameter declarations.
 
 ### Params block