summaryrefslogtreecommitdiff
path: root/doc/ale.txt
diff options
context:
space:
mode:
authorSh3Rm4n <f.vioel@googlemail.com>2019-05-09 13:44:16 +0200
committerSh3Rm4n <f.vioel@googlemail.com>2019-05-09 13:49:44 +0200
commit77c5802fc7490aa6866557cced60c32dcdefa0de (patch)
treea815104028c219bbeba849c21aee77ff0c258237 /doc/ale.txt
parenta223253f35be35b31a6103805a9ed197cd13cdb5 (diff)
downloadale-77c5802fc7490aa6866557cced60c32dcdefa0de.zip
Fix typos in documentation
Diffstat (limited to 'doc/ale.txt')
-rw-r--r--doc/ale.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/ale.txt b/doc/ale.txt
index b777e575..8261050a 100644
--- a/doc/ale.txt
+++ b/doc/ale.txt
@@ -682,7 +682,7 @@ b:ale_echo_msg_format *b:ale_echo_msg_format*
`%s` - replaced with the text for the problem
`%...code...% `- replaced with the error code
`%linter%` - replaced with the name of the linter
- `%severity%` - replaced withe severity of the problem
+ `%severity%` - replaced with the severity of the problem
The strings for `%severity%` can be configured with the following options.
@@ -699,7 +699,7 @@ b:ale_echo_msg_format *b:ale_echo_msg_format*
|g:ale_echo_cursor| needs to be set to 1 for messages to be displayed.
The echo message format can also be configured separately for each buffer,
- so different formats can be used for differnt languages. (Say in ftplugin
+ so different formats can be used for different languages. (Say in ftplugin
files.)
@@ -2459,7 +2459,7 @@ ALELast *ALELast*
Flags can be combined to create create custom jumping. Thus you can use
":ALENext -wrap -error -nosyle" to jump to the next error which is not a
- style error while going back to the begining of the file if needed.
+ style error while going back to the beginning of the file if needed.
`ALEFirst` goes to the first error or warning in the buffer, while `ALELast`
goes to the last one.
@@ -3194,7 +3194,7 @@ ale#statusline#Count(buffer) *ale#statusline#Count()*
ale#statusline#FirstProblem(buffer, type) *ale#statusline#FirstProblem()*
Returns a copy of the first entry in the `loclist` that matches the supplied
- buffer number and problem type. If there is no such enty, an empty dictionary
+ buffer number and problem type. If there is no such entry, an empty dictionary
is returned.
Problem type should be one of the strings listed below: