cleanup file/function names

[peach-html5-editor.git] / README.md

diff --git a/README.md b/README.md
index 02020d6..af50f19 100644 (file)
--- a/README.md
+++ b/README.md
@@ -28,7 +28,7 @@ Quick Start Guide
 
 4.     Try running the parser in the console, example:
 
-               window.wheic.parse_html("<p>foo</p>", {fragment: "body"})
+               window.wheic_parser.parse("<p>foo</p>", {fragment: "body"})
 
 For further reading, see "Running Under node.js" below.
 
@@ -55,25 +55,25 @@ Now you can do any of these things in any order:
 
 *      Run the tests directly from CoffeeScript:
 
-               coffee test.coffee
+               coffee parser_tests.coffee
 
 *      Test the compiled (javascript) parser in your favorite browser by opening
        up ``parser_tests.html`` and looking at the console.
 
 *      Run tests via compiled code:
 
-               nodejs test.js
+               nodejs parser_tests.js
 
 *      Try using the parser in your own javascript node.js project:
 
-               var wheic = require('./parse-html.js');
-               var dom = wheic.parse_html("<p>hi</p>", {fragment: 'body'});
+               var html5 = require('./parser.js');
+               var dom = html5.parse("<p>hi</p>", {fragment: 'body'});
                ...
 
 *      Try using the parser in your own CoffeeScript node.js project:
 
-               wheic = require './parse-html.js'
-               dom = wheic.parse_html "<p>hi</p>", fragment: 'body'
+               html5 = require './parser.js'
+               dom = html5.parse "<p>hi</p>", fragment: 'body'
                ...
 
        Note: the CoffeeScript compile time is significant, so you'll want to use