caret not carat

SoarGroup · Jan 15, 2025 · 957d828 · 957d828
1 parent 220790a
commit 957d828
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/reference/cli/cmd_preferences.md b/docs/reference/cli/cmd_preferences.md
@@ -26,7 +26,7 @@ preferences [options] [identifier [attribute]]
 The `preferences` command prints all the preferences for the given object
 identifier and attribute. If identifier and attribute are not specified, they
 default to the current state and the current operator. The Soar syntax attribute
-carat (`^`) is optional when specifying the attribute. The optional arguments
+caret (`^`) is optional when specifying the attribute. The optional arguments
 indicates the level of detail to print about each preference.
 
 This command is useful for examining which candidate operators have been

diff --git a/docs/soar_manual/03_SyntaxOfSoarPrograms.md b/docs/soar_manual/03_SyntaxOfSoarPrograms.md
@@ -1425,7 +1425,7 @@ since it does not have an `acceptable` preference.
 
 Ambiguity can easily arise when using a preference that can be either binary or
 unary: `> < =`. The default assumption is that if a value follows the
-preference, then the preference is binary. It will be unary if a carat
+preference, then the preference is binary. It will be unary if a caret
 (up-arrow), a closing parenthesis, another preference, or a comma follows it.
 
 Below are four examples of legal, although unrealistic, actions that have the