diff --git a/app/vmauth/README.md b/app/vmauth/README.md
index 3d8af0d80..7959e1c04 100644
--- a/app/vmauth/README.md
+++ b/app/vmauth/README.md
@@ -247,7 +247,7 @@ It is recommended protecting the following endpoints with authKeys:
 * `/metrics` with `metricsAuthKey` command-line flag, so unauthorized users couldn't get access to [vmauth metrics](#monitoring).
 * `/debug/pprof` with `pprofAuthKey` command-line flag, so unauthorized users couldn't get access to [profiling information](#profiling).
 
-`vmauth` also supports the ability to restict access by IP - see [these docs](#ip-filters). See also [concurrency limiting docs](#concurrency-limiting).
+`vmauth` also supports the ability to restrict access by IP - see [these docs](#ip-filters). See also [concurrency limiting docs](#concurrency-limiting).
 
 ## Monitoring
 
diff --git a/docs/vmauth.md b/docs/vmauth.md
index a2073b36e..e9f8bc1e1 100644
--- a/docs/vmauth.md
+++ b/docs/vmauth.md
@@ -258,7 +258,7 @@ It is recommended protecting the following endpoints with authKeys:
 * `/metrics` with `metricsAuthKey` command-line flag, so unauthorized users couldn't get access to [vmauth metrics](#monitoring).
 * `/debug/pprof` with `pprofAuthKey` command-line flag, so unauthorized users couldn't get access to [profiling information](#profiling).
 
-`vmauth` also supports the ability to restict access by IP - see [these docs](#ip-filters). See also [concurrency limiting docs](#concurrency-limiting).
+`vmauth` also supports the ability to restrict access by IP - see [these docs](#ip-filters). See also [concurrency limiting docs](#concurrency-limiting).
 
 ## Monitoring