Textual updates, fix broken links, privacy statement

Author: easydatawarehousing

README.md

@@ -1,6 +1,6 @@
 # TryRuby R4
 
-This repo holds the source of the TryRuby.nl website. TryRuby is a website
+This repo holds the source of the TryRuby website. TryRuby is a website
 where you can learn the Ruby language. Starting from zero knowledge about
 programming you can learn the basics of Ruby in 56 short lessons.
 
@@ -52,7 +52,7 @@ for more background information on how and why this website was created.
 
 ## The MIT License
 
-Copyright (C) 2014-2017 Ivo Herweijer
+Copyright (C) 2014-2018 Ivo Herweijer
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

source/about.html.markdown

@@ -6,7 +6,7 @@ author: Ivo Herweijer
 
 ### The MIT License
 
-Copyright (C) 2014-2017 Ivo Herweijer
+Copyright (C) 2014-2018 Ivo Herweijer
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -46,10 +46,10 @@ Japanese translation by _Koji Shimada_ & _Masayoshi Takahashi_
 
 ### Privacy
 
-TryRuby.nl only uses session cookies. These store language preference and last
-lesson visited. The webserver stores visit information in the Apache
-combined log format. This includes ip address and date/time.
-The webserver that TryRuby.nl runs on is physically located in The Netherlands.
+This website only uses session cookies. These store language preference and last
+lesson visited.
+You can find the privacy statement for the webserver this site is hosted on
+<a href="https://help.github.com/articles/github-privacy-statement/" target="_blank">here</a>.
 
 ### Source code
 

source/articles/2015-01-01-try-ruby-version-4.html.markdown

@@ -8,7 +8,7 @@ the_summary: Some information about the history of TryRuby and the reasons for b
 ## History
 This is the fourth iteration of the TryRuby website.
 TryRuby was originally created by a famous Ruby enthusiast working under the nickname 'why
-the lucky stiff'. You can read more about him on
+the lucky stiff', a.k.a. \_Why. You can read more about him on
 <a href="http://en.wikipedia.org/wiki/Why_the_lucky_stiff" target="_blank">Wikipedia</a>.
 
 \_Why doesn't exist anymore, but TryRuby lives on. It was first recreated by Andrew McElroy
@@ -24,15 +24,8 @@ This fourth iteration of TryRuby was created for several reasons.
 - Lesson content also missed some important information (like __if__ statements)
 - All previous TryRuby versions consisted of an irb interpreter with a web front-end.
   Even though some security measures have been taken (isolating and restricting the irb process
-  and whitelisting input), this still sounds like a disastrously bad idea from a security
-  perspective!  
+  and whitelisting input), this still sounds like a bad idea from a security perspective!  
   TryRuby<sup>R4</sup> runs inside the web browser
-- TryRuby.org is embedded in a commercial venture. This doesn't seem in line with the
-  free spirit in which TryRuby was created
-- Since I have a C/C++ background and am switching to Ruby/Rails, I needed a small but significant
-  Ruby project for my resume.  
-  The original lesson content was brilliant stuff, so working on TryRuby was a most
-  enjoyable experience
 
 ### Changes
 By changing the TryRuby mechanics from running irb on a server, to running Opal in the web browser,
@@ -62,7 +55,3 @@ Your opinion is most welcome:
 - Add some self evaluation questions at the end of each chapter
 - Maybe remove the lessons about classes. It's a bit advanced for an absolute beginners
   course
-- I am hosting TryRuby<sup>R4</sup> using an .nl domain, simply because this was available and
-  is the cheapest option for me.  
-  TryRuby really ought to be part of RubyLang.org
-

source/articles/2015-01-02-testing.html.markdown

@@ -90,7 +90,7 @@ Each feature usually has many scenario's.
 ### Test tools and automation
 Ruby has one of the most advanced set of testing tools available anywhere.
 
-For supporting TDD style testing __rspec__ is very popular.
+For supporting TDD style testing both __rspec__ and __minitest__ are very popular.
 BDD style testing is often done with __cucumber__. Cucumber lets you translate functional
 requirements written in plain English into executable (!) tests for your Ruby code.
 

source/articles/2015-01-03-app-development.html.markdown

@@ -21,7 +21,7 @@ device itself.
 These days, to deliver the service to a customer we really have to support multiple distribution
 channels:
 a website usable from a variety of computers and devices, plus a native app for each of the major
-platforms (Android, iOS, BlackBerry, Windows Phone, Ubuntu, Gecko).
+platforms (Android, iOS, Windows Phone).
 A lot of different technologies to learn!
 
 Life for software developers isn't that simple anymore. What are your options ?
@@ -32,9 +32,9 @@ Web browsers are getting more powerful every year. Giving you better control ove
 and feel of your website, regardless of the size or type of device used by your customer.
 
 But your customer will still need constant internet access to use your service. Fortunately
-the web browser can help us here as well. HTML R5 enabled web browsers support something called
-local storage, which you can use to make the customer think he/she is still connected to your
-service. When an internet connection becomes available again, you can sync changes.
+the web browser can help us here as well. HTML 5 enabled web browsers support something called
+local storage and service workers, which you can use to make the customer think he/she is still
+connected to your service. When an internet connection becomes available again, you can sync changes.
 I am not saying that this is easy to do, far from it, but it's do-able.
 
 One thing that can make life easier is to use <a href="http://opalrb.com/" target="_blank">Opal</a>.
@@ -51,8 +51,8 @@ to support. Native apps give you ultimate control over the look and feel off you
 You will also have better access to the sensors built into the device (movement, position, ...).
 
 Huge drawback to this approach is that every mobile platform uses a completely different development
-environment and programming language. You might need to learn about Java, Objective-C, C-Sharp and others.
+environment and programming language. You might need to learn about Java, Objective-C, Swift,
+C-Sharp and others.
 
-But you are in luck ! With <a href="http://www.rubymotion.com" target="_blank">RubyMotion</a>
-you can create native apps for iOS and Android using your favorite Ruby language.
-It is not free, but it will save you a lot of time !
+But you are in luck ! There are cross-platform tools available where you create you app once and
+distribute it to multiple mobile platforms.

source/articles/2015-01-04-web-development.html.markdown

@@ -37,10 +37,10 @@ There are several other Ruby web frameworks that are simpler and easier to learn
 
 - __Sinatra__  
   Popular: <a href="http://www.sinatrarb.com/" target="_blank">Sinatra</a>
+- __Hanami__  
+  Clever: <a href="http://hanamirb.org/" target="_blank">Hanami</a>
 - __Camping__  
-  Originally crafted by \_why (just like this website): <a href="http://camping.io/" target="_blank">Camping</a>
-- __Grape__  
-  Handy for creating webservices: <a href="http://intridea.github.io/grape/" target="_blank">Grape</a>
+  Originally crafted by \_why (just like this website): <a href="https://github.com/camping/camping" target="_blank">Camping</a>
 - __Ramaze__  
   Simple and few conventions: <a href="http://ramaze.net/" target="_blank">Ramaze</a>
 - __NyNy__