aboutsummaryrefslogtreecommitdiff
path: root/folkwisdom.md
diff options
context:
space:
mode:
authorGravatar Andres Erbsen <andreser@mit.edu>2016-06-25 18:53:38 -0400
committerGravatar Andres Erbsen <andreser@mit.edu>2016-06-25 18:53:38 -0400
commit37382028bef1b752482fb18c9550384e0e9bf0a9 (patch)
treed8bf7d60dd940c35f8ab3390e58b537c2c4886cd /folkwisdom.md
parent3b535970442c9065a57bf4e23ad5c2c4c0b667b6 (diff)
s/quality/equality/
Diffstat (limited to 'folkwisdom.md')
-rw-r--r--folkwisdom.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/folkwisdom.md b/folkwisdom.md
index de72c76f4..92f15036e 100644
--- a/folkwisdom.md
+++ b/folkwisdom.md
@@ -184,7 +184,7 @@ worse. Here are some suggestions.
1. The number one reason for hitting issues with custom equivalence relations is
that either the goal or the givens contain a typo that switched one equivalence
relation with another. In particular, `<>` refers to negation of propositional
-quality by default. This can be avoided with good conventions: when introducing
+equality by default. This can be avoided with good conventions: when introducing
a type that will be used with a custom equivalence relation, introduce the
equivalence relation (and its `Equivalence` instance) right away. When
introducing a function involving a such type, introduce a `Proper` instance