From c626a1b31b4c1491b2763b7db30a31d0fb24d70b Mon Sep 17 00:00:00 2001
From: Tom Kralidis <tomkralidis@gmail.com>
Date: Mon, 30 Dec 2024 22:34:19 -0500
Subject: [PATCH] update RFC5 details

---
 docs/development/rfc/5.md | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/docs/development/rfc/5.md b/docs/development/rfc/5.md
index 26bc40c..793564e 100644
--- a/docs/development/rfc/5.md
+++ b/docs/development/rfc/5.md
@@ -8,7 +8,7 @@ title: RFC5 - Enhanced data limit handling
 - author: Tom Kralidis
 - contact: tomkralidis@gmail.com
 - status: draft
-- modified: 2024-11-19
+- modified: 2024-12-30
 
 ## Overview
 
@@ -31,7 +31,7 @@ limits:
     maxitems: 500  # applies to vector data
     maxdistance: [x, y]  # applies to all datasets
     units: m  # as per UCUM https://ucum.org/ucum#section-Tables-of-Terminal-Symbols
-    on_surpass: error  # one of error, throttle
+    on_exceed: error  # one of error, throttle
 ```
 
 The `limits` setting will be applied as follows:
@@ -44,7 +44,7 @@ The `limits` setting will be applied as follows:
 ## Implementation
 
 - an `evaluate_limit` function will be added to the `pygeoapi` module for use by `pygeoapi.api` accordingly
-- if `limits.on_surpass` is `error`, then pygeoapi will throw HTTP 413
+- if `limits.on_exceed` is `error`, then pygeoapi will throw HTTP 413
 
 ### Backwards Compatibility Issues
 
@@ -62,9 +62,7 @@ Documentation will be added to the configuration description page.
 
 Issue: <https://github.com/geopython/pygeoapi/issues/1856>
 
-Branch: <https://github.com/geopython/pygeoapi/tree/limits>
-
-Pull Request: TBD
+Pull Request: <https://github.com/geopython/pygeoapi/pull/1892>
 
 ## Voting History