From 38620480dd37a64a0b8ceaea70efb1387ecb9168 Mon Sep 17 00:00:00 2001
From: Ashley Wade <107071905+ashnwade@users.noreply.github.com>
Date: Wed, 11 Sep 2024 13:04:13 -0400
Subject: [PATCH] Fix typo

---
 admin/limits.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/admin/limits.md b/admin/limits.md
index 90c0bd05..acf9f91e 100644
--- a/admin/limits.md
+++ b/admin/limits.md
@@ -25,5 +25,5 @@ User-created [resources](/resources/resources) can take up a lot of space on dis
 
 If you're seeing error messages indicating that your resource exceeds the maximum size, consider the following options:
 
-* Consider if you really need all the columns in your lookup table, especially if you're generating the table from a query. If you only need to match MAC addresses to hostnames in your queries, don't say `tag=inventory ax | unique mac | table -save inv_lookup`, because that will build a table with columsn for *every* field on the data; instead, extract only what you need: `tag=inventory ax mac hostname | unique mac | table -save inv_lookup`.
+* Consider if you really need all the columns in your lookup table, especially if you're generating the table from a query. If you only need to match MAC addresses to hostnames in your queries, don't say `tag=inventory ax | unique mac | table -save inv_lookup`, because that will build a table with columns for *every* field on the data; instead, extract only what you need: `tag=inventory ax mac hostname | unique mac | table -save inv_lookup`.
 * If you're building resources to do lookups on IP addresses or subnets, check if the specialized formats used by the [ipexist](/search/ipexist/ipexist) or [iplookup](/search/iplookup/iplookup) modules might be more suitable to your needs. These special types of lookup tables can be more space-efficient for some needs.