From f89d7ee576814c6ebde823b68a0b64bba8c2ad8f Mon Sep 17 00:00:00 2001
From: Wingrez <31106425+wingrez@users.noreply.github.com>
Date: Sun, 21 Jan 2024 17:22:14 +0800
Subject: [PATCH] cmd/compile/internal/ssa: fix typo in sccp

---
 src/cmd/compile/internal/ssa/sccp.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/cmd/compile/internal/ssa/sccp.go b/src/cmd/compile/internal/ssa/sccp.go
index d1e62f73c6..ecc0f94e5b 100644
--- a/src/cmd/compile/internal/ssa/sccp.go
+++ b/src/cmd/compile/internal/ssa/sccp.go
@@ -343,7 +343,7 @@ func computeLattice(f *Func, val *Value, args ...*Value) lattice {
 	// However, this would create a huge switch for all opcodes that can be
 	// evaluated during compile time. Moreover, some operations can be evaluated
 	// only if its arguments satisfy additional conditions(e.g. divide by zero).
-	// It's fragile and error prone. We did a trick by reusing the existing rules
+	// It's fragile and error-prone. We did a trick by reusing the existing rules
 	// in generic rules for compile-time evaluation. But generic rules rewrite
 	// original value, this behavior is undesired, because the lattice of values
 	// may change multiple times, once it was rewritten, we lose the opportunity