fixes typo

supertokens · Aug 26, 2024 · aa2f5ca · aa2f5ca
1 parent acd2c50
commit aa2f5ca
Show file tree

Hide file tree

Showing 6 changed files with 6 additions and 6 deletions.
diff --git a/v2/emailpassword/rate-limits.mdx b/v2/emailpassword/rate-limits.mdx
@@ -13,7 +13,7 @@ import CustomAdmonition from "/src/components/customAdmonition"
 
 ## For managed service
 
-The SuperTokens core is rate limited on a per app and per IP address basis. This means that if query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
+The SuperTokens core is rate limited on a per app and per IP address basis. This means that if you query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
 
 :::note
 To know more about rps and bursts, please [this nginx document](https://www.nginx.com/blog/rate-limiting-nginx/).

diff --git a/v2/passwordless/rate-limits.mdx b/v2/passwordless/rate-limits.mdx
@@ -13,7 +13,7 @@ import CustomAdmonition from "/src/components/customAdmonition"
 
 ## For managed service
 
-The SuperTokens core is rate limited on a per app and per IP address basis. This means that if query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
+The SuperTokens core is rate limited on a per app and per IP address basis. This means that if you query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
 
 :::note
 To know more about rps and bursts, please [this nginx document](https://www.nginx.com/blog/rate-limiting-nginx/).

diff --git a/v2/session/rate-limits.mdx b/v2/session/rate-limits.mdx
@@ -13,7 +13,7 @@ import CustomAdmonition from "/src/components/customAdmonition"
 
 ## For managed service
 
-The SuperTokens core is rate limited on a per app and per IP address basis. This means that if query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
+The SuperTokens core is rate limited on a per app and per IP address basis. This means that if you query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
 
 :::note
 To know more about rps and bursts, please [this nginx document](https://www.nginx.com/blog/rate-limiting-nginx/).

diff --git a/v2/thirdparty/rate-limits.mdx b/v2/thirdparty/rate-limits.mdx
@@ -13,7 +13,7 @@ import CustomAdmonition from "/src/components/customAdmonition"
 
 ## For managed service
 
-The SuperTokens core is rate limited on a per app and per IP address basis. This means that if query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
+The SuperTokens core is rate limited on a per app and per IP address basis. This means that if you query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
 
 :::note
 To know more about rps and bursts, please [this nginx document](https://www.nginx.com/blog/rate-limiting-nginx/).

diff --git a/v2/thirdpartyemailpassword/rate-limits.mdx b/v2/thirdpartyemailpassword/rate-limits.mdx
@@ -13,7 +13,7 @@ import CustomAdmonition from "/src/components/customAdmonition"
 
 ## For managed service
 
-The SuperTokens core is rate limited on a per app and per IP address basis. This means that if query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
+The SuperTokens core is rate limited on a per app and per IP address basis. This means that if you query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
 
 :::note
 To know more about rps and bursts, please [this nginx document](https://www.nginx.com/blog/rate-limiting-nginx/).

diff --git a/v2/thirdpartypasswordless/rate-limits.mdx b/v2/thirdpartypasswordless/rate-limits.mdx
@@ -13,7 +13,7 @@ import CustomAdmonition from "/src/components/customAdmonition"
 
 ## For managed service
 
-The SuperTokens core is rate limited on a per app and per IP address basis. This means that if query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
+The SuperTokens core is rate limited on a per app and per IP address basis. This means that if you query the core for app1 using the same IP address very quickly, the rate limit will kick in and you will get a `429` status code back from the core. However, if you query the core using different IP addresses or for a different app, the rate limit of that won't interfere with the previous requests (that had another IP or was for another app).
 
 :::note
 To know more about rps and bursts, please [this nginx document](https://www.nginx.com/blog/rate-limiting-nginx/).