remove now unneeded cdist-language

Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>

REAL_README

@@ -19,6 +19,9 @@ it ticks differently:
  * cdist is written in POSIX shell
   * No special requirements like high level interpreters needed on server or target
 
+MAIN AIM:  It MUST be incredible easy/dumb to add new types.
+
+
 ### Architecture
 
  * Push mode (server pushes configuration)
@@ -40,6 +43,9 @@ but is not. Or: The reason why I began to write cdist.
  * Consistency in behaviour, naming and documentation
  * Easy integration nacked installations
  * Simple and well-known DSL: posix shell
+ * It is very easy to
+  * extend cdist
+  * debug cdist-core and cdist-types
 
 ## Requirements
 

doc/man/cdist-language.text

@@ -1,44 +0,0 @@
-cdist-language(7)
-=================
-Nico Schottelius <nico-cdist--@--schottelius.org>
-
-
-NAME
-----
-cdist-language - Cdist Configuration language
-
-
-DESCRIPTION
------------
-A cdist configuration consists of the following parts:
-
-- manifests (cdist-manifests(7))
-- library (cdist-language-library(7))
-- modules (cdist-language-modules(7))
-
-- library vs. modules?
-
-Requirements:
-   It MUST be incredible easy/dumb to add new types.
-      => growable default types
-
-   - how to write a module
-      - module function autoloading via *.sh
-      - module "manifest"?
-         - create functions in *.sh 
-         - name functions "modulename_function"
-            module hellow
-            function kitty
-            => hellow_kitty
-
-      - you are advised (not forced) to put files
-         to a subdirectory named "files"
-
-SEE ALSO
---------
-
-
-COPYING
--------
-Copyright \(C) 2010-2011 Nico Schottelius. Free use of this software is
-granted under the terms of the GNU General Public License version 3 (GPLv3).