README.rdoc in timeliness-0.4.4 vs README.rdoc in timeliness-0.4.5

@@ -1,9 +1,9 @@
 = Timeliness {<img src="https://travis-ci.org/adzap/timeliness.svg?branch=master" alt="Build Status" />}[https://travis-ci.org/adzap/timeliness]
 
-* Source:  http://github.com/adzap/timeliness
-* Bugs:    http://github.com/adzap/timeliness/issues
+* Source:  https://github.com/adzap/timeliness
+* Bugs:    https://github.com/adzap/timeliness/issues
 
 == Description
 
 Date/time parser for Ruby with the following features:
 
@@ -14,11 +14,11 @@
 * I18n support (for months), if I18n gem loaded.
 * Fewer WTFs than Time/Date parse method.
 * Has no dependencies.
 * Works with Ruby MRI >= 2.2
 
-Extracted from the {validates_timeliness gem}[http://github.com/adzap/validates_timeliness], it has been rewritten cleaner and much faster. It's most suitable for when
+Extracted from the {validates_timeliness gem}[https://github.com/adzap/validates_timeliness], it has been rewritten cleaner and much faster. It's most suitable for when
 you need to control the parsing behaviour. It's faster than the Time/Date class parse methods, so it
 has general appeal.
 
 
 == Usage
@@ -49,18 +49,18 @@
 ignored.
 
 
 === Specify the Current Date
 
-Notice a time only string will return with a date value. The date value can be configured globally 
+Notice a time only string will return with a date value. The date value can be configured globally
 with this setting:
 
   Timeliness.date_for_time_type = [2010, 1, 1]
 
 or using a lambda thats evaluated when parsed
 
-  Timeliness.date_for_time_type = lambda { Time.now } 
+  Timeliness.date_for_time_type = lambda { Time.now }
 
 It can also be specified with :now option:
 
   Timeliness.parse('12:13:14', now: Time.mktime(2010,9,8)) #=> Wed Sep 08 12:13:14 1000 2010
 
@@ -141,11 +141,11 @@
   require 'timeliness/core_ext'
 
 
 == Formats
 
-The gem has default formats included which can be easily added to using the format syntax. Also 
+The gem has default formats included which can be easily added to using the format syntax. Also
 formats can be easily removed so that they are no longer considered valid.
 
 Below are the default formats. If you think they are easy to read then you will be happy to know
 that is exactly the same format syntax you can use to define your own. No complex regular
 expressions are needed.
@@ -226,11 +226,11 @@
        u = microseconds matches 1 to 3 digits
 
 All other characters are considered literal. For the technically minded, these formats are compiled
 into a single regular expression
 
-To see all defined formats look at the {source code}[http://github.com/adzap/timeliness/tree/master/lib/timeliness/formats.rb].
+To see all defined formats look at the {source code}[https://github.com/adzap/timeliness/tree/master/lib/timeliness/formats.rb].
 
 
 == Settings
 
 === US/Euro Formats
@@ -250,11 +250,11 @@
 
   Timeliness.use_us_formats
 
 ==== Thread Safety
 
-The switching of formats is threadsafe (since v0.4.0), however for each new thread the format default will be 
+The switching of formats is threadsafe (since v0.4.0), however for each new thread the format default will be
 the gem default, being the US format. To control default for your app and each new thread, use the config
 
   Timeliness.ambiguous_date_format = :euro
 
 
@@ -299,10 +299,10 @@
   year of 20 is considered 1920
 
 
 == Credits
 
-* Adam Meehan ([e-mail], http://github.com/adzap)
+* Adam Meehan ([e-mail], https://github.com/adzap)
 
 
 == License
 
 Copyright (c) 2010 Adam Meehan, released under the MIT license