Fix

Author: ncabatoff

content/vault/v1.16.x/content/docs/upgrading/upgrade-to-1.16.x.mdx

@@ -309,4 +309,6 @@ If you use `file` audit devices, you need to:
 
 @include 'known-issues/enterprise-plugins.mdx'
 
+@include '../../../global/partials/important-changes/known-issue/multi-seal-rewrap.mdx'
+
 @include '../../../global/partials/important-changes/known-issue/ssrf-block-endpoint.mdx'

content/vault/v1.18.x/content/docs/upgrading/upgrade-to-1.16.x.mdx

@@ -302,3 +302,5 @@ more details, and information about opt-out.
 @include 'known-issues/sync-activation-flags-cache-not-updated.mdx'
 
 @include 'known-issues/enterprise-plugins.mdx'
+
+@include '../../../global/partials/important-changes/known-issue/multi-seal-rewrap.mdx'

content/vault/v1.19.x/content/docs/updates/important-changes.mdx

@@ -526,4 +526,6 @@ If you have multiple event subscribers with the same namespace and event type
 filters you have two options:
 
 1. Spread them out among the nodes of the Vault cluster.
-1. Only subscribe to events on the active node of the cluster.
+1. Only subscribe to events on the active node of the cluster.
+
+@include '../../../global/partials/important-changes/known-issue/multi-seal-rewrap.mdx'

content/vault/v1.20.x/content/docs/updates/important-changes.mdx

@@ -435,4 +435,6 @@ If you have multiple event subscribers with the same namespace and event type
 filters you have two options:
 
 1. Spread them out among the nodes of the Vault cluster.
-1. Only subscribe to events on the active node of the cluster.
+1. Only subscribe to events on the active node of the cluster.
+
+@include '../../../global/partials/important-changes/known-issue/multi-seal-rewrap.mdx'