@@ -7,23 +7,23 @@ This Clojure style guide recommends best practices so that real-world Clojure
77programmers can write code that can be maintained by other real-world Clojure
88programmers. A style guide that reflects real-world usage gets used, and a
99style guide that holds to an ideal that has been rejected by the people it is
10- supposed to help risks not getting used at all &ndash ; no matter how good it is.
10+ supposed to help risks not getting used at all &mdash ; no matter how good it is.
1111
1212The guide is separated into several sections of related rules. I've
13- tried to add the rationale behind the rules (if it's omitted I've
14- assumed that is pretty obvious).
13+ tried to add the rationale behind the rules (if it's omitted, I've
14+ assumed that it's pretty obvious).
1515
16- I didn't come up with all the rules out of nowhere - they are mostly
16+ I didn't come up with all the rules out of nowhere; they are mostly
1717based on my extensive career as a professional software engineer,
1818feedback and suggestions from members of the Clojure community, and
1919various highly regarded Clojure programming resources, such as
2020[ "Clojure Programming"] ( http://www.clojurebook.com/ )
2121and [ "The Joy of Clojure"] ( http://joyofclojure.com/ ) .
2222
23- The guide is still a work in progress - some sections are missing,
23+ The guide is still a work in progress; some sections are missing,
2424others are incomplete, some rules are lacking examples, some rules
2525don't have examples that illustrate them clearly enough. In due time
26- these issues will be addressed - just keep them in mind for now.
26+ these issues will be addressed & mdash ; just keep them in mind for now.
2727
2828You can generate a PDF or an HTML copy of this guide using
2929[ Transmuter] ( https://github.com/TechnoGate/transmuter ) .
0 commit comments