diff --git a/docs/reference/airnode/latest/migration.md b/docs/reference/airnode/latest/migration.md
index e786f36e..190e2c5e 100644
--- a/docs/reference/airnode/latest/migration.md
+++ b/docs/reference/airnode/latest/migration.md
@@ -20,7 +20,7 @@ tags:
 # {{$frontmatter.title}}
 
 The following guide assumes a valid v0.10.x `config.json` file. All changes
-listed below will need to be implemented in order to migrate to Airnode v0.11.x.
+listed below will need to be implemented in order to migrate to Airnode v0.11.2.
 This document is written in a way that will preserve existing behavior with
 earlier Airnode versions.
 
@@ -29,9 +29,10 @@ such as airnode-deployer, airnode-admin, etc., and new features.
 
 ## Summary
 
-1. `ois[n].oisFormat` updated to "2.0.0".
+1. `ois[n].oisFormat` updated to "2.1.0". Note that Airnode v0.11.0 and v0.11.1
+   use "2.0.0".
 
-2. `nodeSettings.nodeVersion` updated to "0.11.1".
+2. `nodeSettings.nodeVersion` updated to "0.11.2".
 
 3. `ois[n].endpoints[n].preProcessingSpecifications` and
    `ois[n].endpoints[n].postProcessingSpecifications` have an updated allowed
@@ -46,23 +47,23 @@ such as airnode-deployer, airnode-admin, etc., and new features.
 
 1. `ois[n].oisFormat`
 
-Updated to "2.0.0"
+Updated to "2.1.0". Note that Airnode v0.11.0 and v0.11.1 use "2.0.0".
 
 ```diff
 {
 - "oisFormat": "1.4.0"
-+ "oisFormat": "2.0.0"
++ "oisFormat": "2.1.0"
 }
 ```
 
 2. `nodeSettings.nodeVersion`
 
-Updated to "0.11.1"
+Updated to "0.11.2"
 
 ```diff
 {
 - "nodeVersion": "0.10.0"
-+ "nodeVersion": "0.11.1"
++ "nodeVersion": "0.11.2"
 }
 ```
 
@@ -153,5 +154,23 @@ to learn more about this feature.
   [OEV gateway](/reference/airnode/latest/understand/oev-gateway.md) doc to
   learn more about this feature.
 - The heartbeat payload now includes `deployment_id`.
+- The `value` for a `fixedOperationParameters` object is now allowed to be any
+  type, including an object; for example, the following specifies an array
+  containing multiple primitives. Note that this feature is only available
+  beginning in v0.11.2.
+
+  ```json
+  {
+    "fixedOperationParameters": [
+      {
+        "operationParameter": {
+          "in": "query",
+          "name": "params"
+        },
+        "value": ["finalized", false]
+      }
+    ]
+  }
+  ```
 
 <FlexEndTag/>
diff --git a/docs/reference/airnode/next/migration.md b/docs/reference/airnode/next/migration.md
index 0e2d8cea..2e46568c 100644
--- a/docs/reference/airnode/next/migration.md
+++ b/docs/reference/airnode/next/migration.md
@@ -19,8 +19,8 @@ tags:
 
 # {{$frontmatter.title}}
 
-The following guide assumes a valid v0.11.x `config.json` file. All changes
-listed below will need to be implemented in order to migrate to Airnode v0.12.x.
+The following guide assumes a valid v0.11.2 `config.json` file. All changes
+listed below will need to be implemented in order to migrate to Airnode v0.12.0.
 This document is written in a way that will preserve existing behavior with
 earlier Airnode versions.
 
@@ -29,7 +29,8 @@ such as airnode-deployer, airnode-admin, etc., and new features.
 
 ## Summary
 
-1. `ois[n].oisFormat` updated to "2.1.0".
+1. `ois[n].oisFormat` updated to "2.1.0". This has not changed since v0.11.2,
+   but has changed since v0.11.0 and v0.11.1 for which it was "2.0.0".
 
 2. `nodeSettings.nodeVersion` updated to "0.12.0".
 
@@ -37,14 +38,12 @@ such as airnode-deployer, airnode-admin, etc., and new features.
    addresses on chains for which there is an API3 deployment are now optional.
    See details below for additional information.
 
-4. The `value` for a `fixedOperationParameters` object is now allowed to be any
-   type.
-
 ## Details
 
 1. `ois[n].oisFormat`
 
-Updated to "2.1.0"
+Updated to "2.1.0". This has not changed since v0.11.2, but has changed since
+v0.11.0 and v0.11.1 for which it was "2.0.0".
 
 ```diff
 {
@@ -59,7 +58,7 @@ Updated to "0.12.0"
 
 ```diff
 {
-- "nodeVersion": "0.11.1"
+- "nodeVersion": "0.11.2"
 + "nodeVersion": "0.12.0"
 }
 ```
@@ -120,24 +119,6 @@ And second, within the `chains[n].authorizers` object:
 }
 ```
 
-4. The `value` for a `fixedOperationParameters` object is now allowed to be any
-   type, including an object; for example, the following specifies an array
-   containing multiple primitives.
-
-```json
-{
-  "fixedOperationParameters": [
-    {
-      "operationParameter": {
-        "in": "query",
-        "name": "params"
-      },
-      "value": ["finalized", false]
-    }
-  ]
-}
-```
-
 ## New features and updates
 
 - There is no longer a hardcoded limit to the maximum number of sponsor wallet
@@ -149,5 +130,24 @@ And second, within the `chains[n].authorizers` object:
   2. Reserved parameters are inaccessible in response pre/post processing. This
      is only relevant if reserved parameters are being _modified_ in pre/post
      processing (advanced use case).
+- The `value` for a `fixedOperationParameters` object is now allowed to be any
+  type, including an object; for example, the following specifies an array
+  containing multiple primitives. This has not changed since v0.11.2, but has
+  changed since v0.11.0 and v0.11.1 for which it was only allowed to be a
+  string.
+
+  ```json
+  {
+    "fixedOperationParameters": [
+      {
+        "operationParameter": {
+          "in": "query",
+          "name": "params"
+        },
+        "value": ["finalized", false]
+      }
+    ]
+  }
+  ```
 
 <FlexEndTag/>