diff options
| author |  un1versal | 2015-12-09 16:03:50 +0000 |
|---|---|---|
| committer | un1versal | 2015-12-19 02:40:23 +0000 |
| commit | c74db9aba4814ccb4dc0ac1e4c7e4ef7589f50a9 (patch) | |
| tree | 1be38d394b47be8408585a00b2c67819bcf37082 /src/modules/options/OptionsWidget_ctcpFloodProtection.cpp | |
| parent | src/modules: typos, consistency capitalize, fomatting and indenting fixes (diff) | |
| download | KVIrc-c74db9aba4814ccb4dc0ac1e4c7e4ef7589f50a9.tar.gz KVIrc-c74db9aba4814ccb4dc0ac1e4c7e4ef7589f50a9.tar.bz2 KVIrc-c74db9aba4814ccb4dc0ac1e4c7e4ef7589f50a9.zip | |
various files: typos/consistency and capitalization see notes below.
https://techbase.kde.org/Projects/Usability/HIG/Capitalization
This was just done last minute over some notes I had made during earlier similar fixes.
* dont capitalize prepositions/conjunctions with less than 5 letters + fix wrong plural.
* freenode is all lowercase instance only.
* tooltips are not Camel Case capitalization style either.
* some centered text on a dialog when all the etxt is left aligned looks off, tootips we can give a pass to.
* Tree items are Camel Case
* Typos in Unknow channel modes
* more tooltips in the Channel Mode/Ban Masks/Invite but flawed design on these
The tooltips text doubles up as title one isnt capitalized and the other is...
So now none are in this area only since unlike toolbars thers no test display here and its passable.
Alternative is to fix these dialogs and toolbars and tbh I cant do it.
* cannot vs can't : these are consistency fixes for strings and debug messages only.
* about dialog group titles "Runtime Info" "Build Info" are Camel Cased as per capitalization guidelines, but label are like all other labels.
s spaces
tyyt
Diffstat (limited to 'src/modules/options/OptionsWidget_ctcpFloodProtection.cpp')
| -rw-r--r-- | src/modules/options/OptionsWidget_ctcpFloodProtection.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/modules/options/OptionsWidget_ctcpFloodProtection.cpp b/src/modules/options/OptionsWidget_ctcpFloodProtection.cpp index b26d8e2df..387e80902 100644 --- a/src/modules/options/OptionsWidget_ctcpFloodProtection.cpp +++ b/src/modules/options/OptionsWidget_ctcpFloodProtection.cpp @@ -58,7 +58,7 @@ respond to within the interval of time defined in the second field.[br] A strong protection against floods would be replying to 4 requests every 20 seconds.[br] The minimum effective setting is about 3 messages every 6 seconds.[br] - Please note that 3 messages every 6 seconds is NOT the same as 10 messages every 20 seconds; + Please note that 3 messages every 6 seconds is [b]not[/b] the same as 10 messages every 20 seconds; the first setting would allow 3 requests within one second, but the client would ignore all the requests for the next 5 seconds, the second setting would allow 10 messages within one second and ignore everything for the next 19 seconds. Therefore, 3/6 is a safer setting.[br] |