diff --git a/docs/_spec/components/schemas/array-max-monitored-elements.yaml b/docs/_spec/components/schemas/array-max-monitored-elements.yaml
index 2a370be..0030c54 100644
--- a/docs/_spec/components/schemas/array-max-monitored-elements.yaml
+++ b/docs/_spec/components/schemas/array-max-monitored-elements.yaml
@@ -169,7 +169,7 @@ common-proposal-status:
 
         The number of facilities for this provider whose Ratings Obligation has
         not been met in this forecast window. This number may be larger than the
-        size of `incomplete-facilities`, since the latter has a pre-defined
+        size of `incomplete-obligations`, since the latter has a pre-defined
         upper bound for performance and application security reasons.
 
         The Ratings Provider should check that this value is zero when they
@@ -190,7 +190,7 @@ common-proposal-status:
         case for this set is debugging and troubleshooting.
 
       minItems: 0
-      maxItems: 10
+      maxItems: *max-facilities
       items:
         $ref: ./names.yaml
 
diff --git a/docs/example-narratives/submitting-forecasts.md b/docs/example-narratives/submitting-forecasts.md
index d870dd6..c8a363b 100644
--- a/docs/example-narratives/submitting-forecasts.md
+++ b/docs/example-narratives/submitting-forecasts.md
@@ -125,7 +125,7 @@ defines `incomplete-obligation-count`:
 
 > The number of facilities for this provider whose Ratings Obligation has
 > not been met in this forecast window. This number may be larger than the
-> size of `incomplete-facilities`, since the latter has a pre-defined
+> size of `incomplete-obligations`, since the latter has a pre-defined
 > upper bound for performance and application security reasons.
 
 > The Ratings Provider should check that this value is zero when they