summaryrefslogtreecommitdiff
path: root/sys/dev
diff options
context:
space:
mode:
authorandvar <andvar@NetBSD.org>2022-04-12 20:51:42 +0000
committerandvar <andvar@NetBSD.org>2022-04-12 20:51:42 +0000
commit79fb736f4b9e0c5a74db99c2ee08d7570bba93f7 (patch)
tree16ed85bf18550d54cc049c78892ae6b31a9b4f4a /sys/dev
parentb79c293c1db19ebaae879813edeaea91a7ec4d7b (diff)
s/similarily/similarly/
Diffstat (limited to 'sys/dev')
-rw-r--r--sys/dev/ic/ispvar.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/sys/dev/ic/ispvar.h b/sys/dev/ic/ispvar.h
index efc35f7e6e5..ea4f401d19d 100644
--- a/sys/dev/ic/ispvar.h
+++ b/sys/dev/ic/ispvar.h
@@ -1,4 +1,4 @@
-/* $NetBSD: ispvar.h,v 1.74 2021/09/11 20:28:06 andvar Exp $ */
+/* $NetBSD: ispvar.h,v 1.75 2022/04/12 20:51:42 andvar Exp $ */
/*
* Copyright (C) 1999 National Aeronautics & Space Administration
* All rights reserved.
@@ -395,9 +395,9 @@ typedef struct {
* index to put it into the Database, but that's just an optimization. We mark
* the entry VALID and make sure that the target index is updated and correct.
*
- * When we get done searching the local loop, we then search similarily for
+ * When we get done searching the local loop, we then search similarly for
* a list of devices we've gotten from the fabric name controller (if we're
- * on a fabric). VALID marking is also done similarily.
+ * on a fabric). VALID marking is also done similarly.
*
* When all of this is done, we can march through the database and clean up
* any entry that is still PROBATIONAL (these represent devices which have