Commit 494e181

authored

Merge pull request #48 from bpringe/master

Typos in readme

2 parents 707f16d + fb20afa commit 494e181Copy full SHA for 494e181

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -48,7 +48,7 @@ they do better?". After all, Joda-Time already provides a pretty comprehensive`
`48`	`48`	`set of tools for dealing with time-related concepts. Turns out, it's a tad more`
`49`	`49`	`complicated than it has to be. Also, a few concepts have faulty designs which`
`50`	`50`	`lead to hard to fix bugs and misuse. You can see the birds-eye view of changes`
`51`		`-and some of the rationale on the authors' (Stephen Colebourne) blog:`
	`51`	`+and some of the rationale on the author's (Stephen Colebourne) blog:`
`52`	`52`
`53`	`53`	`* [what's wrong with Joda-Time](http://blog.joda.org/2009/11/why-jsr-310-isn-joda-time_4941.html),`
`54`	`54`	`* [when you should use Java-Time](http://blog.joda.org/2014/07/threeten-backport-vs-joda-time.html)`
@@ -438,7 +438,7 @@ the `Inst` protocol and the Joda-Time types are external to the library.
`438`	`438`
`439`	`439`	Java Time introduced a concept of `Clock` - a time entity which can seed the
`440`	`440`	`dates, times and zones. However, there's no built-in facility which would allow`
`441`		`-you to influence the date-times create using default constructors ala Joda's`
	`441`	`+you to influence the date-times created using default constructors ala Joda's`
`442`	`442`	`DateTimeUtils/setCurrentMillisSystem`. Clojure.Java-Time tries to fix that with
`443`	`443`	the `with-clock` macro and the corresponding `with-clock-fn` function:
`444`	`444`

Comments

(0)