joerg 2004/01/12 08:21:05
Modified: src/blocks/woody/samples/flow bindings.js
Log:
fixed typos
Revision Changes Path
1.3 +4 -4 cocoon-2.1/src/blocks/woody/samples/flow/bindings.js
Index: bindings.js
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/blocks/woody/samples/flow/bindings.js,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- bindings.js 31 Dec 2003 14:37:13 -0000 1.2
+++ bindings.js 12 Jan 2004 16:21:05 -0000 1.3
@@ -52,10 +52,10 @@
/**
* Disclaimer:
* To make this flowscript quite generic we've applied some typical
javascript
- * hacks here and there. Don't let them overwhelm you, the prupose of this
tutorial
- * is _not_ to get into the depths of woody and flowscript. In stead you
should
+ * hacks here and there. Don't let them overwhelm you, the purpose of this
tutorial
+ * is _not_ to get into the depths of woody and flowscript. Instead you
should
* focus on the effects of the applied definitions in the binding files:
- * see ../forms/bindings/*-bind.xml. And how to shape you backend-models:
+ * see ../forms/bindings/*-bind.xml. And how to shape your backend-models:
* - for JS see here: createJSBeanfor*() functions
* - for Java see the org.apache.cocoon.woody.samples.bindings.* classes
* - for XML see ../forms/bindings/*-data.xml.
@@ -83,7 +83,7 @@
/**
* Generic entry-function for all binding samples. This uses the
* 'sample-code' and the 'backend-type' to effectively select the form
- * and specific back-end-model to use.
+ * and specific backend-model to use.
*/
function bindingSample(sampleCode, backendType) {
// sample-code holds the number-and-name of this binding sample in the
tutorial
