From cb26f548339b52138ea620dec7f782aae8adca92 Mon Sep 17 00:00:00 2001
From: Anirvan Chatterjee <57606+anirvan@users.noreply.github.com>
Date: Fri, 28 Jan 2022 16:06:46 -0800
Subject: [PATCH] =?utf8?q?Fix=20typo=20("vary=20long"=20=E2=80=94>=20"very?=
 =?utf8?q?=20long")?=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

---
 bin/perltidy | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bin/perltidy b/bin/perltidy
index 218e309e..f922a76a 100755
--- a/bin/perltidy
+++ b/bin/perltidy
@@ -456,7 +456,7 @@ A problem arises using a fixed maximum line length with very deeply nested code
 and data structures because eventually the amount of leading whitespace used
 for indicating indentation takes up most or all of the available line width,
 leaving little or no space for the actual code or data.  One solution is to use
-a vary long line length.  Another solution is to use the B<-vmll> flag, which
+a very long line length.  Another solution is to use the B<-vmll> flag, which
 basically tells perltidy to ignore leading whitespace when measuring the line
 length.
 
-- 
2.39.5