From dc19fa1b79ea7e1a268b5c9b03676d18a8212c9e Mon Sep 17 00:00:00 2001 From: Morten Haraldsen Date: Mon, 27 Feb 2017 09:10:07 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c352c27..9fc31af 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ There are an endless amount of APIs with non-standard date/time exchange, and th Some projects use epoch time-stamps for date-time exchange, and from a performance perspective this *may* make sense in *extreme* cases. With this project one can do-the-right-thing and maintain performance in date-time handling. -* What is wrong with epoc timestamps?* +*What is wrong with epoch timestamps?* * It is not human-readable, so debugging and direct manipulation is harder * Limited resolution and/or time-range available