Merge pull request #1 from treffynnon/gh-pages

update repository

LICENCE

@@ -1,7 +1,5 @@
 SQL style guide (c) by Simon Holywell <https://www.simonholywell.com/>
 
-SQL style guide is licensed under a
+This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.
-Creative Commons Attribution-ShareAlike 4.0 International License.
+To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/ or send a letter
-
+to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA.
-You should have received a copy of the license along with this
-work. If not, see <http://creativecommons.org/licenses/by-sa/4.0/>. 

README.md

@@ -27,6 +27,8 @@ If your project uses this styleguide and you'd like to be mentioned in this read
 please open a pull request adding it below in alphabetical order with a URL and short
 description.
 
+* [BEdita](https://github.com/bedita/bedita) - a Symfony based PHP CMF
+* [SQLQuery.jl](https://github.com/yeesian/SQLQuery.jl) - A Julia lang package for representing sql queries, and converting them to valid SQL statements
 * [Stock Talk](https://github.com/nigelgilbert/stock-talk) - a realtime dashboard that displays the stock data of the most Tweeted Nasdaq companies.
 
 ## Notable forks of the guide

_includes/foot.html

@@ -1,11 +1,33 @@
 <footer class="foot wrap">
     <hr/>
+    <p>
+        This guide is being discussed on Hacker News [
+            <a href="https://news.ycombinator.com/item?id=9941150">1</a>,
+            <a href="https://news.ycombinator.com/item?id=12671667">2</a>
+        ],
+        Reddit [
+            <a href="https://www.reddit.com/r/SQL/comments/3efmn0/sql_style_guide_a_consistent_code_guide_ensuring/">1</a>,
+            <a href="https://www.reddit.com/r/programming/comments/3eri42/sql_style_guide_by_simon_holywell/">2</a>,
+            <a href="https://www.reddit.com/r/PHP/comments/3efmp7/sql_style_guide_a_consistent_code_guide_ensuring/">3</a>
+        ],
+        <a href="https://lobste.rs/s/q9elee/sql_style_guide_by_simon_holywell">Lobste.rs</a> and
+        of course <a href="https://twitter.com/search?f=tweets&q=&quot;sqlstyle.guide&quot;">Twitter</a>
+        if you want to have your say.
+    </p>
+    <p>
+        I have attempted to answer most of the frequently asked questions and held misconceptions in a blog post
+        entitled "<a href="https://www.simonholywell.com/post/2016/12/sql-style-guide-misconceptions/">SQL style
+        guide misconceptions</a>" please have a read.
+    </p>
+    <p>Please do <a href="https://github.com/treffynnon/sqlstyle.guide/issues">open issues</a> or
+        <a href="https://github.com/treffynnon/sqlstyle.guide/pulls/">pull requests</a> for any errors you
+        may find in the guide and help me to improve it.</p>
     <p>
         <span xmlns:dct="http://purl.org/dc/terms/" property="dct:title">
             SQL style guide
         </span> by
         <a xmlns:cc="http://creativecommons.org/ns#"
-           href="https://www.simonholywell.com/?utm_source=sqlstyle.guide&utm_medium=link&utm_campaign=footer-licence"
+           href="https://www.simonholywell.com/?utm_source=sqlstyle.guide&amp;utm_medium=link&amp;utm_campaign=footer-licence"
            property="cc:attributionName"
            rel="cc:attributionURL">
             Simon Holywell

_includes/sqlstyle.guide.md

@@ -33,7 +33,7 @@ Based on a work at [http://www.sqlstyle.guide][self].
 * Keep code succinct and devoid of redundant SQL—such as unnecessary quoting or
   parentheses or `WHERE` clauses that can otherwise be derived.
 * Include comments in SQL code where necessary. Use the C style opening `/*` and
-  closing `*/` where possible otherwise preceed comments with `--` and finish
+  closing `*/` where possible otherwise precede comments with `--` and finish
   them with a new line.
 
 ```sql