update groovy version in examples

docs/getting-started/policies.md

@@ -276,7 +276,7 @@ The attributes:
 - `fromVersion` and `toVersion` - define the version range;
 - `value` - new dependency value.
 
-For example, updating groovy dependency version to 2.5.21:
+For example, updating groovy dependency version to `2.5.21`:
 
 ```json
 {

docs/getting-started/scripting.md

@@ -253,14 +253,14 @@ requires the addition of a dependency to
 [groovy-all](https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/) and
 the identifier `groovy`. For versions 2.4.* and lower jar packaging is used in
 projects, so the correct dependency is
-e.g. `mvn://org.codehaus.groovy:groovy-all:2.4.12`. Versions 2.5.0 and higher
+e.g. `mvn://org.codehaus.groovy:groovy-all:2.4.12`. Versions `2.5.0` and higher
 use pom packaging, which has to be added to the dependency declaration before
-the version `mvn://org.codehaus.groovy:groovy-all:pom:2.5.2`.
+the version. For example: `mvn://org.codehaus.groovy:groovy-all:pom:2.5.21`.
 
 ```yaml
 configuration:
   dependencies:
-  - "mvn://org.codehaus.groovy:groovy-all:pom:2.5.2"
+  - "mvn://org.codehaus.groovy:groovy-all:pom:2.5.21"
 flows:
   default:
   - script: groovy
@@ -289,7 +289,7 @@ Maps:
 ```yaml
 configuration:
   dependencies:
-    - "mvn://org.codehaus.groovy:groovy-all:pom:2.5.2"
+    - "mvn://org.codehaus.groovy:groovy-all:pom:2.5.21"
 
 flows:
   default:

docs/processes-v1/configuration.md

@@ -167,13 +167,13 @@ The `mvn` syntax uses the short form for GAV coordinates
 Newer versions of groovy-all use `<packaging>pom</packaging>` and define
 dependencies. To use a project that applies this approach, called Bill of
 Material (BOM), as a dependency you need to specify the packaging in between
-the artifactId and version. For example, version 2.5.2 has to be specified as
-`org.codehaus.groovy:groovy-all:pom:2.5.2`:
+the artifactId and version. For example, version `2.5.21` has to be specified as
+`org.codehaus.groovy:groovy-all:pom:2.5.21`:
 
 ```yaml
 configuration:
   dependencies:
-  - "mvn://org.codehaus.groovy:groovy-all:pom:2.5.2"
+  - "mvn://org.codehaus.groovy:groovy-all:pom:2.5.21"
 ```
 
 The same logic and syntax usage applies to all other dependencies including

docs/processes-v2/configuration.md

@@ -188,13 +188,13 @@ The `mvn` syntax uses the short form for GAV coordinates
 Newer versions of groovy-all use `<packaging>pom</packaging>` and define
 dependencies. To use a project that applies this approach, called Bill of
 Material (BOM), as a dependency you need to specify the packaging in between
-the artifactId and version. For example, version 2.5.2 has to be specified as
-`org.codehaus.groovy:groovy-all:pom:2.5.2`:
+the artifactId and version. For example, version `2.5.21` has to be specified as
+`org.codehaus.groovy:groovy-all:pom:2.5.21`:
 
 ```yaml
 configuration:
   dependencies:
-  - "mvn://org.codehaus.groovy:groovy-all:pom:2.5.2"
+  - "mvn://org.codehaus.groovy:groovy-all:pom:2.5.21"
 ```
 
 The same logic and syntax usage applies to all other dependencies including

training/includes/concord-1-beginner-4-details.md

@@ -553,7 +553,7 @@ Dependency:
 ```yaml
 configuration:
   dependencies:
-  - "mvn://org.codehaus.groovy:groovy-all:pom:2.5.2"
+  - "mvn://org.codehaus.groovy:groovy-all:pom:2.5.21"
 ```
 
 Inline script: