starting to rename to rubyx

lib/register/builtin/README.md

@@ -13,6 +13,6 @@ A normal ruby function is one that is parsed and transformed to code. But not al
 be written in ruby, one of those chicken and egg things.
 C uses Assembler in this situation, we use Builtin functions.
 
-Slightly more here : http://salama.github.io/2014/06/10/more-clarity.html (then still called Kernel)
+Slightly more here : http://ruby-x.org/2014/06/10/more-clarity.html (then still called Kernel)
 
 The Builtin module is scattered into several files, but that is just so the file doesn't get too long.

lib/typed/parfait/README.md

@@ -9,8 +9,8 @@ And a large part of that functionality must actually be used at compile time too
 We reuse the Parfait code at compile-time, to create the data for the compiled vm.
 To do this the vm (re) defines the object memory (in parfait_adapter).
 
-A work in progress that started from here : http://salama.github.io/2014/06/10/more-clarity.html
-went on here http://salama.github.io/2014/07/05/layers-vs-passes.html
+A work in progress that started from here : http://ruby-x.org/2014/06/10/more-clarity.html
+went on here http://ruby-x.org/2014/07/05/layers-vs-passes.html
 
 A step back:  the code (program) we compile runs at run - time.
 And so does parfait. So all we have to do is compile it with the program.

lib/typed/parfait/object.rb

@@ -54,7 +54,7 @@ module Parfait
     # This is the crux of the object system. The class of an object is stored in the objects
     # memory (as opposed to an integer that has no memory and so always has the same class)
     #
-    # In Salama we store the class in the Type, and so the Type is the only fixed
+    # In RubyX we store the class in the Type, and so the Type is the only fixed
     # data that every object carries.
     def get_class()
       l = get_type()