summaryrefslogtreecommitdiff
path: root/docs/topics/i18n/timezones.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics/i18n/timezones.txt')
-rw-r--r--docs/topics/i18n/timezones.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt
index bf97d40761..53e2af24df 100644
--- a/docs/topics/i18n/timezones.txt
+++ b/docs/topics/i18n/timezones.txt
@@ -19,8 +19,8 @@ practice to store data in UTC in your database. The main reason is daylight
saving time (DST). Many countries have a system of DST, where clocks are moved
forward in spring and backward in autumn. If you're working in local time,
you're likely to encounter errors twice a year, when the transitions happen.
-This probably doesn't matter for your blog, but it's a problem if you over-bill
-or under-bill your customers by one hour, twice a year, every year. The
+This probably doesn't matter for your blog, but it's a problem if you overbill
+or underbill your customers by one hour, twice a year, every year. The
solution to this problem is to use UTC in the code and use local time only when
interacting with end users.