diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml
index b09f6e3d..83dbed5b 100644
--- a/.github/workflows/docs.yml
+++ b/.github/workflows/docs.yml
@@ -11,11 +11,11 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Inject env variables
-        uses: rlespinasse/github-slug-action@v3.x
-      - uses: actions/setup-node@v3
+        uses: rlespinasse/github-slug-action@v4
+      - uses: actions/setup-node@v4
         with:
           node-version: 'lts/*'
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - run: |
           npm install
           npm run generate
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
index 25659365..8781b1fa 100644
--- a/.github/workflows/tests.yml
+++ b/.github/workflows/tests.yml
@@ -4,10 +4,10 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/setup-node@v3
+      - uses: actions/setup-node@v4
         with:
           node-version: 'lts/*'
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - name: Run linter
         run: |
           npm install
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 559e73d3..5e6784e3 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -16,13 +16,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - `clip`: Throw an exception if min > max [#472](https://github.com/Open-EO/openeo-processes/issues/472)
 - `save_results`: Returns the STAC resource instead of boolean `true` [API#376](https://github.com/Open-EO/openeo-api/issues/376)
+- Added a uniqueness contraint to various array-typed parameters (e.g. lists of dimension names or labels)
+- Renamed `create_data_cube` to `create_cube`. [#68](https://github.com/Open-EO/openeo-processes/issues/68)
+- `apply_polygon`: Renamed `polygons` parameter to `geometries` for better alignment with other geometry handling processes. [#511](https://github.com/Open-EO/openeo-processes/issues/511)
 
 ### Fixed
 
+- Clarified for various mathematical functions the defined input and output ranges. Mention that `NaN` is returned outside of the defined input range where possible.
+- `aggregate_temporal` and `aggregate_temporal_period`: Clarified that the process throws a `DimensionNotAvailable` exception when no temporal dimension exists.
+- `aggregate_temporal_period`: Removed unused exception `DistinctDimensionLabelsRequired`
+- `aggregate_temporal_period`: Clarified that the definition of weeks follows ISO 8601
+- `divide`: Clarified behavior for division by 0
 - `between`: Clarify that `null` is passed through.
 - `eq` and `neq`: Explicitly set the minimum value for the `delta` parameter.
 - `filter_bbox`, `load_collection`, `load_stac`: Clarified that the bounding box is reprojected to the CRS of the spatial data cube dimensions if required.
 - `filter_spatial`: Clarified that masking is applied using the given geometries. [#469](https://github.com/Open-EO/openeo-processes/issues/469)
+- `mod`: Clarified behavior for y = 0
 - `sqrt`: Clarified that NaN is returned for negative numbers.
 
 ## [2.0.0-rc.1] - 2023-05-25
diff --git a/absolute.json b/absolute.json
index 3b6e91dc..c6a3713d 100644
--- a/absolute.json
+++ b/absolute.json
@@ -1,7 +1,7 @@
 {
     "id": "absolute",
     "summary": "Absolute value",
-    "description": "Computes the absolute value of a real number `x`, which is the \"unsigned\" portion of x and often denoted as *|x|*.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the absolute value of a real number `x`, which is the \"unsigned\" portion of `x` and often denoted as *|x|*.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math"
     ],
@@ -95,4 +95,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/aggregate_temporal.json b/aggregate_temporal.json
index ad1d560b..2c66e0f2 100644
--- a/aggregate_temporal.json
+++ b/aggregate_temporal.json
@@ -128,6 +128,7 @@
             "description": "Distinct labels for the intervals, which can contain dates and/or times. Is only required to be specified if the values for the start of the temporal intervals are not distinct and thus the default labels would not be unique. The number of labels and the number of groups need to be equal.",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "items": {
                     "type": [
                         "number",
@@ -140,7 +141,7 @@
         },
         {
             "name": "dimension",
-            "description": "The name of the temporal dimension for aggregation. All data along the dimension is passed through the specified reducer. If the dimension is not set or set to `null`, the data cube is expected to only have one temporal dimension. Fails with a `TooManyDimensions` exception if it has more dimensions. Fails with a `DimensionNotAvailable` exception if the specified dimension does not exist.",
+            "description": "The name of the temporal dimension for aggregation. All data along the dimension is passed through the specified reducer. If the dimension is not set or set to `null`, the data cube is expected to only have one temporal dimension. Fails with a `TooManyDimensions` exception if it has more dimensions. Fails with a `DimensionNotAvailable` exception if the specified dimension does not exist or no temporal dimension is available.",
             "schema": {
                 "type": [
                     "string",
@@ -228,7 +229,7 @@
             "message": "The data cube contains multiple temporal dimensions. The parameter `dimension` must be specified."
         },
         "DimensionNotAvailable": {
-            "message": "A dimension with the specified name does not exist."
+            "message": "A dimension with the specified name does not exist or no temporal dimension is available."
         },
         "DistinctDimensionLabelsRequired": {
             "message": "The dimension labels have duplicate values. Distinct labels must be specified."
diff --git a/aggregate_temporal_period.json b/aggregate_temporal_period.json
index bdaea43e..446afa8d 100644
--- a/aggregate_temporal_period.json
+++ b/aggregate_temporal_period.json
@@ -23,7 +23,7 @@
         },
         {
             "name": "period",
-            "description": "The time intervals to aggregate. The following pre-defined values are available:\n\n* `hour`: Hour of the day\n* `day`: Day of the year\n* `week`: Week of the year\n* `dekad`: Ten day periods, counted per year with three periods per month (day 1 - 10, 11 - 20 and 21 - end of month). The third dekad of the month can range from 8 to 11 days. For example, the third dekad of a year spans from January 21 till January 31 (11 days), the fourth dekad spans from February 1 till February 10 (10 days) and the sixth dekad spans from February 21 till February 28 or February 29 in a leap year (8 or 9 days respectively).\n* `month`: Month of the year\n* `season`: Three month periods of the calendar seasons (December - February, March - May, June - August, September - November).\n* `tropical-season`: Six month periods of the tropical seasons (November - April, May - October).\n* `year`: Proleptic years\n* `decade`: Ten year periods ([0-to-9 decade](https://en.wikipedia.org/wiki/Decade#0-to-9_decade)), from a year ending in a 0 to the next year ending in a 9.\n* `decade-ad`: Ten year periods ([1-to-0 decade](https://en.wikipedia.org/wiki/Decade#1-to-0_decade)) better aligned with the anno Domini (AD) calendar era, from a year ending in a 1 to the next year ending in a 0.",
+            "description": "The time intervals to aggregate. The following pre-defined values are available:\n\n* `hour`: Hour of the day\n* `day`: Day of the year\n* `week`: Week of the year as defined in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601#Week_dates)\n* `dekad`: Ten day periods, counted per year with three periods per month (day 1 - 10, 11 - 20 and 21 - end of month). The third dekad of the month can range from 8 to 11 days. For example, the third dekad of a year spans from January 21 till January 31 (11 days), the fourth dekad spans from February 1 till February 10 (10 days) and the sixth dekad spans from February 21 till February 28 or February 29 in a leap year (8 or 9 days respectively).\n* `month`: Month of the year\n* `season`: Three month periods of the calendar seasons (December - February, March - May, June - August, September - November).\n* `tropical-season`: Six month periods of the tropical seasons (November - April, May - October).\n* `year`: Proleptic years\n* `decade`: Ten year periods ([0-to-9 decade](https://en.wikipedia.org/wiki/Decade#0-to-9_decade)), from a year ending in a 0 to the next year ending in a 9.\n* `decade-ad`: Ten year periods ([1-to-0 decade](https://en.wikipedia.org/wiki/Decade#1-to-0_decade)) better aligned with the anno Domini (AD) calendar era, from a year ending in a 1 to the next year ending in a 0.",
             "schema": {
                 "type": "string",
                 "enum": [
@@ -78,7 +78,7 @@
         },
         {
             "name": "dimension",
-            "description": "The name of the temporal dimension for aggregation. All data along the dimension is passed through the specified reducer. If the dimension is not set or set to `null`, the source data cube is expected to only have one temporal dimension. Fails with a `TooManyDimensions` exception if it has more dimensions. Fails with a `DimensionNotAvailable` exception if the specified dimension does not exist.",
+            "description": "The name of the temporal dimension for aggregation. All data along the dimension is passed through the specified reducer. If the dimension is not set or set to `null`, the source data cube is expected to only have one temporal dimension. Fails with a `TooManyDimensions` exception if it has more dimensions. Fails with a `DimensionNotAvailable` exception if the specified dimension does not exist or no temporal dimension is available.",
             "schema": {
                 "type": [
                     "string",
@@ -115,10 +115,7 @@
             "message": "The data cube contains multiple temporal dimensions. The parameter `dimension` must be specified."
         },
         "DimensionNotAvailable": {
-            "message": "A dimension with the specified name does not exist."
-        },
-        "DistinctDimensionLabelsRequired": {
-            "message": "The dimension labels have duplicate values. Distinct labels must be specified."
+            "message": "A dimension with the specified name does not exist or no temporal dimension is available."
         }
     },
     "links": [
diff --git a/arccos.json b/arccos.json
index 5ffbce35..4cd498a7 100644
--- a/arccos.json
+++ b/arccos.json
@@ -1,29 +1,32 @@
 {
     "id": "arccos",
     "summary": "Inverse cosine",
-    "description": "Computes the arc cosine of `x`. The arc cosine is the inverse function of the cosine so that *`arccos(cos(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the arc cosine of `x`. The arc cosine is the inverse function of the cosine so that *`arccos(cos(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated. `NaN` is returned for values outside of the allowed range.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number.",
+            "description": "A number in the range *[-1, 1]*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimum": -1,
+                "maximum": 1
             }
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed angle in radians in the range *[0, π]*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimum": 0
         }
     },
     "examples": [
@@ -41,4 +44,4 @@
             "title": "Inverse cosine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/arcosh.json b/arcosh.json
index 6ed581fe..820b8cd4 100644
--- a/arcosh.json
+++ b/arcosh.json
@@ -1,29 +1,31 @@
 {
     "id": "arcosh",
     "summary": "Inverse hyperbolic cosine",
-    "description": "Computes the inverse hyperbolic cosine of `x`. It is the inverse function of the hyperbolic cosine so that *`arcosh(cosh(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the inverse hyperbolic cosine of `x`. It is the inverse function of the hyperbolic cosine so that *`arcosh(cosh(x)) = x`*.\n\nThe no-data value `null` is passed through and therefore gets propagated. `NaN` is returned for values outside of the allowed range.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number.",
+            "description": "A number in the range *[1, +∞)*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
                 ]
-            }
+            },
+            "minimum": 1
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed hyperbolic angle in radians in the range *[0, +∞)*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimum": 0
         }
     },
     "examples": [
@@ -41,4 +43,4 @@
             "title": "Inverse hyperbolic cosine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/arcsin.json b/arcsin.json
index e37eb2d3..2c772a00 100644
--- a/arcsin.json
+++ b/arcsin.json
@@ -1,24 +1,26 @@
 {
     "id": "arcsin",
     "summary": "Inverse sine",
-    "description": "Computes the arc sine of `x`. The arc sine is the inverse function of the sine so that *`arcsin(sin(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the arc sine of `x`. The arc sine is the inverse function of the sine so that *`arcsin(sin(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated. `NaN` is returned for values < -1 and > 1.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number.",
+            "description": "A number in the range *[-1, 1]*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimum": -1,
+                "maximum": 1
             }
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed angle in radians in the range *[-π/2, π/2]*.",
         "schema": {
             "type": [
                 "number",
@@ -41,4 +43,4 @@
             "title": "Inverse sine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/arctan.json b/arctan.json
index dc8d5a68..9461eba3 100644
--- a/arctan.json
+++ b/arctan.json
@@ -18,7 +18,7 @@
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed angle in radians in the range *(−π/2, π/2)*.",
         "schema": {
             "type": [
                 "number",
@@ -41,4 +41,4 @@
             "title": "Inverse tangent explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/arsinh.json b/arsinh.json
index 37384dcd..2b7942dd 100644
--- a/arsinh.json
+++ b/arsinh.json
@@ -1,7 +1,7 @@
 {
     "id": "arsinh",
     "summary": "Inverse hyperbolic sine",
-    "description": "Computes the inverse hyperbolic sine of `x`. It is the inverse function of the hyperbolic sine so that *`arsinh(sinh(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the inverse hyperbolic sine of `x`. It is the inverse function of the hyperbolic sine so that *`arsinh(sinh(x)) = x`*.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math > trigonometric"
     ],
@@ -18,7 +18,7 @@
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed hyperbolic angle in radians.",
         "schema": {
             "type": [
                 "number",
@@ -41,4 +41,4 @@
             "title": "Inverse hyperbolic sine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/artanh.json b/artanh.json
index 926b48ea..6308290d 100644
--- a/artanh.json
+++ b/artanh.json
@@ -1,24 +1,26 @@
 {
     "id": "artanh",
     "summary": "Inverse hyperbolic tangent",
-    "description": "Computes the inverse hyperbolic tangent of `x`. It is the inverse function of the hyperbolic tangent so that *`artanh(tanh(x)) = x`*.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the inverse hyperbolic tangent of `x`. It is the inverse function of the hyperbolic tangent so that *`artanh(tanh(x)) = x`*.\n\nThe no-data value `null` is passed through and therefore gets propagated. `NaN` is returned for values outside of the allowed range. The computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, `x` = 1 results in +infinity and `x` = 0 results in -infinity. Otherwise, an exception is thrown.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number.",
+            "description": "A number in the range *(-1, 1)*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimumExclusive": -1,
+                "maximumExclusive": 1
             }
         }
     ],
     "returns": {
-        "description": "The computed angle in radians.",
+        "description": "The computed hyperbolic angle in radians.",
         "schema": {
             "type": [
                 "number",
@@ -39,6 +41,11 @@
             "rel": "about",
             "href": "http://mathworld.wolfram.com/InverseHyperbolicTangent.html",
             "title": "Inverse hyperbolic tangent explained by Wolfram MathWorld"
+        },
+        {
+            "rel": "about",
+            "href": "https://ieeexplore.ieee.org/document/4610935",
+            "title": "IEEE Standard 754-2008 for Floating-Point Arithmetic"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/cos.json b/cos.json
index 6e6e4143..0d6229a8 100644
--- a/cos.json
+++ b/cos.json
@@ -18,12 +18,14 @@
         }
     ],
     "returns": {
-        "description": "The computed cosine of `x`.",
+        "description": "The computed cosine in the range *[-1, 1]*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimum": -1,
+            "maximum": 1
         }
     },
     "examples": [
@@ -41,4 +43,4 @@
             "title": "Cosine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/cosh.json b/cosh.json
index 975958a4..8b56a222 100644
--- a/cosh.json
+++ b/cosh.json
@@ -1,14 +1,14 @@
 {
     "id": "cosh",
     "summary": "Hyperbolic cosine",
-    "description": "Computes the hyperbolic cosine of `x`.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the hyperbolic cosine of `x`.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "An angle in radians.",
+            "description": "An hyperbolic angle in radians.",
             "schema": {
                 "type": [
                     "number",
@@ -18,12 +18,13 @@
         }
     ],
     "returns": {
-        "description": "The computed hyperbolic cosine of `x`.",
+        "description": "The computed hyperbolic cosine in the range *[1, +∞)*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimum": 1
         }
     },
     "examples": [
@@ -41,4 +42,4 @@
             "title": "Hyperbolic cosine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/create_data_cube.json b/create_cube.json
similarity index 95%
rename from create_data_cube.json
rename to create_cube.json
index 55f0aede..0f8c7ca2 100644
--- a/create_data_cube.json
+++ b/create_cube.json
@@ -1,5 +1,5 @@
 {
-    "id": "create_data_cube",
+    "id": "create_cube",
     "summary": "Create an empty data cube",
     "description": "Creates a new data cube without dimensions. Dimensions can be added with ``add_dimension()``.",
     "categories": [
diff --git a/dev/docs.html b/dev/docs.html
index 04b1c192..0a7d005e 100644
--- a/dev/docs.html
+++ b/dev/docs.html
@@ -5,7 +5,7 @@
     <meta http-equiv="x-ua-compatible" content="ie=edge">
     <title>openEO API Processes</title>
     <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:300,400,400i,700|Roboto+Mono">
-    <script src="https://cdn.jsdelivr.net/npm/vue@2.6"></script>
+    <script src="https://cdn.jsdelivr.net/npm/vue@2.7"></script>
     <script src="https://cdn.jsdelivr.net/npm/@openeo/processes-docgen@1/dist/DocGen.umd.min.js"></script>
     <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@openeo/processes-docgen@1/dist/DocGen.css">
     <style>
@@ -115,7 +115,9 @@
           categorize: true,
           apiVersion: '1.2.0',
           title: 'openEO processes (2.0.0-rc.1)',
-          notice: '**Note:** This is the list of all processes specified by the openEO project. Back-ends implement a varying set of processes. Thus, the processes you can use at a specific back-end may derive from the specification, may include non-standardized processes and may not implement all processes listed here. Please check each back-end individually for the processes they support. The client libraries usually have a function called `listProcesses` or `list_processes` for that.'
+          notice: '**Note:** This is the list of all processes specified by the openEO project. Back-ends implement a varying set of processes. Thus, the processes you can use at a specific back-end may derive from the specification, may include non-standardized processes and may not implement all processes listed here. Please check each back-end individually for the processes they support. The client libraries usually have a function called `listProcesses` or `list_processes` for that.',
+          showExperimentalByDefault: true,
+          showDeprecatedByDefault: false,
         }
       })
     });
diff --git a/divide.json b/divide.json
index 5dd664f1..0c6c254a 100644
--- a/divide.json
+++ b/divide.json
@@ -1,7 +1,7 @@
 {
     "id": "divide",
     "summary": "Division of two numbers",
-    "description": "Divides argument `x` by the argument `y` (*`x / y`*) and returns the computed result.\n\nNo-data values are taken into account so that `null` is returned if any element is such a value.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, a division by zero results in ±infinity if the processing environment supports it. Otherwise, a `DivisionByZero` exception must the thrown.",
+    "description": "Divides argument `x` by the argument `y` (*`x / y`*) and returns the computed result.\n\nNo-data values are taken into account so that `null` is returned if any element is such a value.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. A division by zero results in:\n\n- +infinity for `x` > 0,\n- -infinity for `x` < 0,\n- `NaN` for `x` = 0,\n- or otherwise, throws a `DivisionByZero` exception if the other options are not supported by the processing environment.",
     "categories": [
         "math"
     ],
@@ -76,4 +76,4 @@
             "title": "IEEE Standard 754-2019 for Floating-Point Arithmetic"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/exp.json b/exp.json
index 5a5e3283..2d551390 100644
--- a/exp.json
+++ b/exp.json
@@ -18,12 +18,13 @@
         }
     ],
     "returns": {
-        "description": "The computed value for *e* raised to the power of `p`.",
+        "description": "The computed value for *e* raised to the power of `p`. Value is in the range of *(0, +∞)*",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimumExclusive": 0
         }
     },
     "examples": [
@@ -65,4 +66,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/ln.json b/ln.json
index e073c7a2..1663771b 100644
--- a/ln.json
+++ b/ln.json
@@ -1,19 +1,20 @@
 {
     "id": "ln",
     "summary": "Natural logarithm",
-    "description": "The natural logarithm is the logarithm to the base *e* of the number `x`, which equals to using the *log* process with the base set to *e*. The natural logarithm is the inverse function of taking *e* to the power x.\n\nThe no-data value `null` is passed through.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, *`ln(0)`* results in ±infinity if the processing environment supports it or otherwise an exception is thrown.",
+    "description": "The natural logarithm is the logarithm to the base *e* of the number `x`, which equals to using the *log* process with the base set to *e*. The natural logarithm is the inverse function of taking *e* to the power x.\n\nThe no-data value `null` is passed through.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, *`ln(0)`* results in -infinity if the processing environment supports it or otherwise an exception is thrown. `NaN` is returned for values outside of the allowed range.",
     "categories": [
         "math > exponential & logarithmic"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number to compute the natural logarithm for.",
+            "description": "A number to compute the natural logarithm for in the range *[0, +∞)*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimum": 0
             }
         }
     ],
@@ -64,4 +65,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/log.json b/log.json
index 89500837..67a19ba2 100644
--- a/log.json
+++ b/log.json
@@ -1,19 +1,20 @@
 {
     "id": "log",
     "summary": "Logarithm to a base",
-    "description": "Logarithm to the base `base` of the number `x` is defined to be the inverse function of taking b to the power of x.\n\nThe no-data value `null` is passed through and therefore gets propagated if any of the arguments is `null`.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, `log(0, 2)` results in ±infinity if the processing environment supports it or otherwise an exception is thrown.",
+    "description": "Logarithm to the base `base` of the number `x` is defined to be the inverse function of taking b to the power of x.\n\nThe no-data value `null` is passed through and therefore gets propagated if any of the arguments is `null`.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, having `x` set to `0` with any base results in -infinity if the processing environment supports it or otherwise an exception is thrown. `NaN` is returned for values outside of the allowed range.",
     "categories": [
         "math > exponential & logarithmic"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "A number to compute the logarithm for.",
+            "description": "A number to compute the logarithm for in the range *[0, +∞)*.",
             "schema": {
                 "type": [
                     "number",
                     "null"
-                ]
+                ],
+                "minimum": 0
             }
         },
         {
@@ -78,4 +79,4 @@
             "title": "IEEE Standard 754-2019 for Floating-Point Arithmetic"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/meta/implementation.md b/meta/implementation.md
index e1d5dde9..ac424a2f 100644
--- a/meta/implementation.md
+++ b/meta/implementation.md
@@ -31,16 +31,17 @@ the evaluation should stop and provide the result directly.
 This is basically the same behavior that is also described in the processes `all` and `any`.
 
 For example, the condition `A > 0 or B > 0` should only execute `B > 0` if `A > 0` is false as
-otherwise the result is already unambiguous and will be `true` regardless of the rest of the 
+otherwise the result is already unambiguous and will be `true` regardless of the rest of the
 condition.
 
-Implementing this behavior does not have any negative side-effects so that 
+Implementing this behavior does not have any negative side-effects so that
 comparability and reproducibility of the results is still given.
 
 ## Enums for processing methods
 
 There are numerours processes that provide a predefined set of processing methods.
 For example:
+
 - `ard_surface_reflectance`: `atmospheric_correction_method` and `cloud_detection_method`
 - `athmospheric_correction`: `method`
 - `cloud_detection`: `method`
@@ -63,12 +64,13 @@ This applies similarly to other enums specied in parameter schemas, e.g. the
 
 The processes mentioned above have all at least one parameter for proprietary
 options that can be passed to the corresponsing `methods`:
+
 - `ard_surface_reflectance`: `atmospheric_correction_options` and `cloud_detection_options`
 - `athmospheric_correction`: `options`
 - `cloud_detection`: `options`
 
 By default, the parameters don't allow any value except an empty opject.
-Back-ends have to either remove the parameter or define schema to give user 
+Back-ends have to either remove the parameter or define schema to give user
 details about the supported parameters per supported method.
 
 For example, if you support the methods `iCor` and `FORCE` in `atmospheric_correction`,
@@ -76,40 +78,39 @@ you may define something like the following for the parameter:
 
 ```json
 {
-	"description": "Proprietary options for the atmospheric correction method.",
-	"name": "options",
-	"optional": true,
-	"default": {},
-	"schema": [
-		{
-			"title": "FORCE options",
-			"type": "object",
-			"properties": {
-				"force_option1": {
-					"type": "number",
-					"description": "Description for option 1",
-					"default": 0
-				},
-				"force_option2": {
-					"type": "boolean",
-					"description": "Description for option 1",
-					"default": true
-				}
-			}
-		},
-		{
-			"title": "iCor options",
-			"type": "object",
-			"properties": {
-				"icor_option1": {
-					"type": "string",
-					"description": "Description for option 1",
-					"default": "example"
-				}
-			}
-		}
-
-	]
+  "description": "Proprietary options for the atmospheric correction method.",
+  "name": "options",
+  "optional": true,
+  "default": {},
+  "schema": [
+    {
+      "title": "FORCE options",
+      "type": "object",
+      "properties": {
+        "force_option1": {
+          "type": "number",
+          "description": "Description for option 1",
+          "default": 0
+        },
+        "force_option2": {
+          "type": "boolean",
+          "description": "Description for option 1",
+          "default": true
+        }
+      }
+    },
+    {
+      "title": "iCor options",
+      "type": "object",
+      "properties": {
+        "icor_option1": {
+          "type": "string",
+          "description": "Description for option 1",
+          "default": "example"
+        }
+      }
+    }
+  ]
 }
 ```
 
@@ -149,24 +150,26 @@ Back-ends should not execute the processes for log levels that are not matching
 
 ### Data Types
 
-The process is only useful for users if a common behavior for data types passed into the `data` parameter has been agreed on across implementations. 
+The process is only useful for users if a common behavior for data types passed into the `data` parameter has been agreed on across implementations.
 
 The following chapters include some proposals for common data (sub) types, but it is incomplete and will be extended in the future.
 Also, for some data types a JSON encoding is missing, we'll add more details once agreed upon:
 <https://github.com/Open-EO/openeo-processes/issues/299>
 
 #### Scalars
+
 For the data types boolean, numbers, strings and null it is recommended to log them as given.
 
 #### Arrays
 
 It is recommended to summarize arrays as follows:
+
 ```js
 {
-	"data": [3,1,6,4,8], // Return a reasonable excerpt of the data, e.g. the first 5 or 10 elements
-	"length": 10, // Return the length of the array, this is important to determine whether the data above is complete or an excerpt
-	"min": 0, // optional: Return additional statstics if possible, ideally use the corresponsing openEO process names as keys
-	"max": 10
+  "data": [3,1,6,4,8], // Return a reasonable excerpt of the data, e.g. the first 5 or 10 elements
+  "length": 10, // Return the length of the array, this is important to determine whether the data above is complete or an excerpt
+  "min": 0, // optional: Return additional statstics if possible, ideally use the corresponsing openEO process names as keys
+  "max": 10
 }
 ```
 
@@ -178,38 +181,38 @@ The top-level object and/or each dimension can be enhanced with additional stats
 
 ```js
 {
-	"cube:dimensions": {
-		"x": {
-			"type": "spatial",
-			"axis": "x",
-			"extent": [8.253, 12.975],
-			"reference_system": 4326
-		},
-		"y": {
-			"type": "spatial",
-			"axis": "y",
-			"extent": [51.877,55.988],
-			"reference_system": 4326
-		},
-		"t": {
-			"type": "temporal",
-			"values": [
-				"2015-06-21T12:56:55Z",
-				"2015-06-23T09:12:14Z",
-				"2015-06-25T23:44:44Z",
-				"2015-06-27T21:11:34Z",
-				"2015-06-30T17:33:12Z"
-			],
-			"step": null
-		},
-		"bands": {
-			"type": "bands",
-			"values": ["NDVI"]
-		}
-	},
-	// optional: Return additional data or statstics for the data cube if possible (see also the chapter for "Arrays" above).
-	"min": -1,
-	"max": 1
+  "cube:dimensions": {
+    "x": {
+      "type": "spatial",
+      "axis": "x",
+      "extent": [8.253, 12.975],
+      "reference_system": 4326
+    },
+    "y": {
+      "type": "spatial",
+      "axis": "y",
+      "extent": [51.877,55.988],
+      "reference_system": 4326
+    },
+    "t": {
+      "type": "temporal",
+      "values": [
+        "2015-06-21T12:56:55Z",
+        "2015-06-23T09:12:14Z",
+        "2015-06-25T23:44:44Z",
+        "2015-06-27T21:11:34Z",
+        "2015-06-30T17:33:12Z"
+      ],
+      "step": null
+    },
+    "bands": {
+      "type": "bands",
+      "values": ["NDVI"]
+    }
+  },
+  // optional: Return additional data or statstics for the data cube if possible (see also the chapter for "Arrays" above).
+  "min": -1,
+  "max": 1
 }
 ```
 
@@ -221,10 +224,11 @@ To improve interoperability openEO processes, version 1.2.0 added details about
 A survey has shown that most libraries implement type 7 and as such this was chosen to be the default.
 
 We have found some libraries that can be used for an implementation:
+
 - Java: [Apache Commons Math Percentile](http://commons.apache.org/proper/commons-math/javadocs/api-3.6/org/apache/commons/math3/stat/descriptive/rank/Percentile.html), choose the [estimation type `R_7`](http://commons.apache.org/proper/commons-math/javadocs/api-3.6/org/apache/commons/math3/stat/descriptive/rank/Percentile.EstimationType.html#R_7)
 - JavaScript: [d3](https://github.com/d3/d3-array/blob/v2.8.0/README.md#quantile), has only type 7 implemented.
 - Julia: [Statistics.quantile](https://docs.julialang.org/en/v1/stdlib/Statistics/#Statistics.quantile!), type 7 is the default.
-- Python: [numpy](https://numpy.org/doc/stable/reference/generated/numpy.quantile.html), [pandas](https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.quantile.html), [xarray](http://xarray.pydata.org/en/stable/generated/xarray.DataArray.quantile.html) - type 7 (called 'linear' for the interpolation parameter) is the default for all of them. 
+- Python: [numpy](https://numpy.org/doc/stable/reference/generated/numpy.quantile.html), [pandas](https://pandas.pydata.org/docs/reference/api/pandas.DataFrame.quantile.html), [xarray](http://xarray.pydata.org/en/stable/generated/xarray.DataArray.quantile.html) - type 7 (called 'linear' for the interpolation parameter) is the default for all of them.
 - R: [quantile](https://stat.ethz.ch/R-manual/R-patched/library/stats/html/quantile.html) - type 7 is the default.
 
 ## STAC support
diff --git a/mod.json b/mod.json
index ca709386..0c8a6ea9 100644
--- a/mod.json
+++ b/mod.json
@@ -1,7 +1,7 @@
 {
     "id": "mod",
     "summary": "Modulo",
-    "description": "Remainder after a division of `x` by `y` for both integers and floating-point numbers.\n\nThe result of a modulo operation has the sign of the divisor. The handling regarding the sign of the result [differs between programming languages](https://en.wikipedia.org/wiki/Modulo_operation#In_programming_languages) and needs careful consideration to avoid unexpected results.\n\nThe no-data value `null` is passed through and therefore gets propagated if any of the arguments is `null`. A modulo by zero results in ±infinity if the processing environment supports it. Otherwise, a `DivisionByZero` exception must the thrown.",
+    "description": "Remainder after a division of `x` by `y` for both integers and floating-point numbers.\n\nThe result of a modulo operation has the sign of the divisor. The handling regarding the sign of the result [differs between programming languages](https://en.wikipedia.org/wiki/Modulo_operation#In_programming_languages) and needs careful consideration to avoid unexpected results.\n\nThe no-data value `null` is passed through and therefore gets propagated if any of the arguments is `null`. If `y` is set to 0 this results in:\n\n- +infinity for `x` > 0,\n- -infinity for `x` < 0,\n- `NaN` for `x` = 0,\n- or otherwise, throws a `DivisionByZero` exception if the other options are not supported by the processing environment.",
     "categories": [
         "math"
     ],
@@ -92,4 +92,4 @@
             "title": "Modulo explained by Wikipedia"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/proposals/apply_polygon.json b/proposals/apply_polygon.json
index 735226a1..21ef51fe 100644
--- a/proposals/apply_polygon.json
+++ b/proposals/apply_polygon.json
@@ -16,7 +16,7 @@
             }
         },
         {
-            "name": "polygons",
+            "name": "geometries",
             "description": "A vector data cube containing at least one polygon. The provided vector data can be one of the following:\n\n* A `Polygon` or `MultiPolygon` geometry,\n* a `Feature` with a `Polygon` or `MultiPolygon` geometry, or\n* a `FeatureCollection` containing at least one `Feature` with `Polygon` or `MultiPolygon` geometries.\n* Empty geometries are ignored.",
             "schema": {
                 "type": "object",
diff --git a/proposals/array_create_labeled.json b/proposals/array_create_labeled.json
index 8b5d2034..f83d6559 100644
--- a/proposals/array_create_labeled.json
+++ b/proposals/array_create_labeled.json
@@ -19,6 +19,7 @@
             "description": "An array of labels to be used.",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "items": {
                     "type": [
                         "number",
@@ -43,4 +44,4 @@
             "message": "The number of values in the parameters `data` and `labels` don't match."
         }
     }
-}
\ No newline at end of file
+}
diff --git a/proposals/flatten_dimensions.json b/proposals/flatten_dimensions.json
index da3647ab..1c02bf39 100644
--- a/proposals/flatten_dimensions.json
+++ b/proposals/flatten_dimensions.json
@@ -20,6 +20,7 @@
             "description": "The names of the dimension to combine. The order of the array defines the order in which the dimension labels and values are combined (see the example in the process description). Fails with a `DimensionNotAvailable` exception if at least one of the specified dimensions does not exist.",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "items": {
                     "type": "string"
                 }
diff --git a/proposals/predict_curve.json b/proposals/predict_curve.json
index 479b7fec..ef3e9596 100644
--- a/proposals/predict_curve.json
+++ b/proposals/predict_curve.json
@@ -68,6 +68,7 @@
                 },
                 {
                     "type": "array",
+                    "uniqueItems": true,
                     "items": {
                         "anyOf": [
                             {
diff --git a/proposals/unflatten_dimension.json b/proposals/unflatten_dimension.json
index 990e7469..a5a4bb6d 100644
--- a/proposals/unflatten_dimension.json
+++ b/proposals/unflatten_dimension.json
@@ -27,6 +27,7 @@
             "description": "The names of the new target dimensions. New dimensions will be created with the given names and type `other` (see ``add_dimension()``). Fails with a `TargetDimensionExists` exception if any of the dimensions exists.\n\nThe order of the array defines the order in which the dimensions and dimension labels are added to the data cube (see the example in the process description).",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "minItems": 2,
                 "items": {
                     "type": "string"
diff --git a/rename_labels.json b/rename_labels.json
index 2042737d..de4f07da 100644
--- a/rename_labels.json
+++ b/rename_labels.json
@@ -26,6 +26,7 @@
             "description": "The new names for the labels.\n\nIf a target dimension label already exists in the data cube, a `LabelExists` exception is thrown.",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "items": {
                     "type": [
                         "number",
@@ -39,6 +40,7 @@
             "description": "The original names of the labels to be renamed to corresponding array elements in the parameter `target`. It is allowed to only specify a subset of labels to rename, as long as the `target` and `source` parameter have the same length. The order of the labels doesn't need to match the order of the dimension labels in the data cube. By default, the array is empty so that the dimension labels in the data cube are expected to be enumerated.\n\nIf the dimension labels are not enumerated and the given array is empty, the `LabelsNotEnumerated` exception is thrown. If one of the source dimension labels doesn't exist, the `LabelNotAvailable` exception is thrown.",
             "schema": {
                 "type": "array",
+                "uniqueItems": true,
                 "items": {
                     "type": [
                         "number",
diff --git a/sgn.json b/sgn.json
index f59afdc4..ecdbd9d1 100644
--- a/sgn.json
+++ b/sgn.json
@@ -23,6 +23,12 @@
             "type": [
                 "number",
                 "null"
+            ],
+            "enum": [
+                -1,
+                0,
+                1,
+                null
             ]
         }
     },
@@ -104,4 +110,4 @@
             "result": true
         }
     }
-}
\ No newline at end of file
+}
diff --git a/sin.json b/sin.json
index 06c45cc4..15285979 100644
--- a/sin.json
+++ b/sin.json
@@ -18,12 +18,14 @@
         }
     ],
     "returns": {
-        "description": "The computed sine of `x`.",
+        "description": "The computed sine in the range *[-1, 1]*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimum": -1,
+            "maximum": 1
         }
     },
     "examples": [
@@ -41,4 +43,4 @@
             "title": "Sine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/sinh.json b/sinh.json
index c505b3a3..6eced19c 100644
--- a/sinh.json
+++ b/sinh.json
@@ -1,14 +1,14 @@
 {
     "id": "sinh",
     "summary": "Hyperbolic sine",
-    "description": "Computes the hyperbolic sine of `x`.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the hyperbolic sine of `x`.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "An angle in radians.",
+            "description": "An hyperbolic angle in radians.",
             "schema": {
                 "type": [
                     "number",
@@ -18,7 +18,7 @@
         }
     ],
     "returns": {
-        "description": "The computed hyperbolic sine of `x`.",
+        "description": "The computed hyperbolic sine.",
         "schema": {
             "type": [
                 "number",
@@ -41,4 +41,4 @@
             "title": "Hyperbolic sine explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/tan.json b/tan.json
index c3952efa..6e927ffc 100644
--- a/tan.json
+++ b/tan.json
@@ -1,7 +1,7 @@
 {
     "id": "tan",
     "summary": "Tangent",
-    "description": "Computes the tangent of `x`. The tangent is defined to be the sine of x divided by the cosine of x.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the tangent of `x`. The tangent is defined to be the sine of x divided by the cosine of x.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.\n\nThe computations follow [IEEE Standard 754](https://ieeexplore.ieee.org/document/8766229) whenever the processing environment supports it. Therefore, *`tan(pi()/2 + multipliy(pi(), n))`* with `n` being any integer results in ±infinity. -infinity for negative values passed to `tan`, +infinity otherwise. If the processing environment does not supports it, an exception is thrown.",
     "categories": [
         "math > trigonometric"
     ],
@@ -18,7 +18,7 @@
         }
     ],
     "returns": {
-        "description": "The computed tangent of `x`.",
+        "description": "The computed tangent.",
         "schema": {
             "type": [
                 "number",
@@ -39,6 +39,11 @@
             "rel": "about",
             "href": "http://mathworld.wolfram.com/Tangent.html",
             "title": "Tangent explained by Wolfram MathWorld"
+        },
+        {
+            "rel": "about",
+            "href": "https://ieeexplore.ieee.org/document/4610935",
+            "title": "IEEE Standard 754-2008 for Floating-Point Arithmetic"
         }
     ]
-}
\ No newline at end of file
+}
diff --git a/tanh.json b/tanh.json
index 203f581e..a38462c9 100644
--- a/tanh.json
+++ b/tanh.json
@@ -1,14 +1,14 @@
 {
     "id": "tanh",
     "summary": "Hyperbolic tangent",
-    "description": "Computes the hyperbolic tangent of `x`. The tangent is defined to be the hyperbolic sine of x divided by the hyperbolic cosine of x.\n\nWorks on radians only.\nThe no-data value `null` is passed through and therefore gets propagated.",
+    "description": "Computes the hyperbolic tangent of `x`. The tangent is defined to be the hyperbolic sine of x divided by the hyperbolic cosine of x.\n\nThe no-data value `null` is passed through and therefore gets propagated.",
     "categories": [
         "math > trigonometric"
     ],
     "parameters": [
         {
             "name": "x",
-            "description": "An angle in radians.",
+            "description": "An hyperbolic angle in radians.",
             "schema": {
                 "type": [
                     "number",
@@ -18,12 +18,14 @@
         }
     ],
     "returns": {
-        "description": "The computed hyperbolic tangent of `x`.",
+        "description": "The computed hyperbolic tangent in the range *(-1, 1)*.",
         "schema": {
             "type": [
                 "number",
                 "null"
-            ]
+            ],
+            "minimumExclusive": -1,
+            "maximumExclusive": 1
         }
     },
     "examples": [
@@ -41,4 +43,4 @@
             "title": "Hyperbolic tangent explained by Wolfram MathWorld"
         }
     ]
-}
\ No newline at end of file
+}