Fix a few typos
| ... | ... |
@@ -80,7 +80,7 @@ is able to score based on the optimal match. |
| 80 | 80 |
## TextMate |
| 81 | 81 |
|
| 82 | 82 |
TextMate deserves immense credit for popularizing fuzzy finding from inside |
| 83 |
-text editors. It's influence can be found in the commant-t project, various |
|
| 83 |
+text editors. It's influence can be found in the command-t project, various |
|
| 84 | 84 |
other editors use command-t for file finding, and the 't' command in the github |
| 85 | 85 |
web interface. |
| 86 | 86 |
|
| ... | ... |
@@ -101,7 +101,7 @@ The wy `last_idx` is suspicious. |
| 101 | 101 |
## Length of shortest first match: fzf |
| 102 | 102 |
https://github.com/junegunn/fzf/blob/master/src/algo/algo.go |
| 103 | 103 |
|
| 104 |
-Fzy scores based on the size of the greedy shortest match. fzf finds it's match |
|
| 104 |
+Fzy scores based on the size of the greedy shortest match. fzf finds its match |
|
| 105 | 105 |
by the first match appearing in the candidate string. It has some cleverness to |
| 106 | 106 |
find if there is a shorter match contained in that search, but it isn't |
| 107 | 107 |
guaranteed to find the shortest match in the string. |
| ... | ... |
@@ -137,7 +137,7 @@ Example results for the search "abc" |
| 137 | 137 |
* <tt>x**ABXC**x</tt> |
| 138 | 138 |
* <tt>x**ABXC**xbc</tt> |
| 139 | 139 |
|
| 140 |
-The third result here shoud have been scored the same as the first, but the |
|
| 140 |
+The third result here should have been scored the same as the first, but the |
|
| 141 | 141 |
lower scoring but shorter match is what is measured. |
| 142 | 142 |
|
| 143 | 143 |
|