more cleanup and removal of the term "litorgy"

README.markdown

@@ -1,9 +1,6 @@
-rorg --- R and org-mode
+org-babel --- enabling communication between programming languages and between people
 ======================
 
-* for information on R see the [R website](http://www.r-project.org/)
 * for information on org see the [Org-Mode website](http://org-mode.org)
-
-Probably would be good to place the main objectives here, once they
-are ironed out.
-
+* for information on org-babel see the org-babel.org file in this
+  directory

intro.org

@@ -32,8 +32,8 @@
   from the code buffer to view it embedded within an org buffer, which
   may also contain chunks of code in other languages.
   
-* Litorgy
-  Litorgy provides several extensions to the above-described method of
+* Org-Babel
+  Org-Babel provides several extensions to the above-described method of
   working with source code in org mode:
   1. Code block execution for interpreted languages (python, ruby, shell, R, perl)
   2. [...]

org-babel-requirements.org

@@ -720,7 +720,7 @@ useful (I use it all the time).
       
 
 * Buffer Dictionary
- LocalWords:  DBlocks dblocks org-babel el eric litorgical fontification
+ LocalWords:  DBlocks dblocks org-babel el eric fontification
 
 
 

org-babel.org

@@ -56,8 +56,8 @@ pie(dirs[,1], labels = dirs[,2])
 
 ** communication between people
 
-*** calculation in/on tables (litorgies own tests)
-litorgies own functional tests are contained in a large org-mode
+*** calculation in/on tables (org-babels own tests)
+org-babels own functional tests are contained in a large org-mode
 table, allowing the test suite to be run be evaluation of the table
 and the results to be collected in the same table.
 
@@ -98,7 +98,7 @@ how should we share org-babel?
 we need to think up some good examples
 
 **** interactive tutorials
-This could be a place to use [[* litorgical assertions][litorgical assertions]].
+This could be a place to use [[* org-babel assertions][org-babel assertions]].
 
 for example the first step of a tutorial could assert that the version
 of the software-package (or whatever) is equal to some value, then
@@ -505,13 +505,13 @@ We would just need to cycle over every source code block under the
 sandbox, run it, and assert that the return value is equal to what we
 expect.
 
-I have the feeling that this should be possible using only litorgical
+I have the feeling that this should be possible using only org-babel
 functions with minimal or no additional elisp.  It would be very cool
 for org-babel to be able to test itself.
 
 This is now done, see [[* Tests]].
 
-*** DEFERRED litorgical assertions (may not be necessary)
+*** DEFERRED org-babel assertions (may not be necessary)
 These could be used to make assertions about the results of a
 source-code block.  If the assertion fails then the point could be
 moved to the block, and error messages and highlighting etc... could
@@ -534,7 +534,7 @@ ensue
 ** DONE integration with org tables
 We should make it easy to call org-babel source blocks from org-mode
 table formulas.  This is practical now that it is possible to pass
-arguments to litorgical source blocks.
+arguments to org-babel source blocks.
 
 See the related [[* (sandbox) integration w/org tables][sandbox]] header for tests/examples.
 

test-export.org

@@ -1,4 +1,4 @@
-#+TITLE: Testing Litorgy Export
+#+TITLE: Testing Org-Babel Export
 #+OPTIONS: toc:2 ^:nil
 
 * all