diff --git a/doc/en/Authoring/GeoGebra.md b/doc/en/Authoring/GeoGebra.md index 9ee9378b54cd53dcb4751bead2b9df645620c730..323300ff0f3aa657d0414161ba51dbc9ca5b2576 100644 --- a/doc/en/Authoring/GeoGebra.md +++ b/doc/en/Authoring/GeoGebra.md @@ -66,7 +66,7 @@ By default points are free to manipulate in the applet, unless you add `__fixed` Notes 1. No checking is done that the object in STACK matches one in GeoGebra. If it does not exist it will be created by GeoGebra. -2. Currently setting points and values are the only supported objects. Users can set objects, e.g. you could define `g:x^3` and set this in an appletm +2. Currently setting points and values are the only supported objects. Users can set objects, e.g. you could define `g:x^3` and set this in an applet. 3. Angles cannot be set directly, set points instead! @@ -126,7 +126,7 @@ Recall that since the object in `watch="A"` is written in upper case it must be Then complete the question as follows. -1. The question expects an in input `A`. In this input, make the model answer `ta1`. This is a list, and has a different name from the watched point.. +1. The question expects an input `A`. In this input, make the model answer `ta1`. This is a list, and has a different name from the watched point.. 2. Make sure you set "forbid floats" option in the input to be false, if you want to! 3. Complete the default potential response tree `prt1` as `ATAlgEquiv(ntupleify(A), ntupleify(ta1))` diff --git a/doc/en/Authoring/Testing.md b/doc/en/Authoring/Testing.md index 6cbd567106fa8627e591b5afc35a711bfa38cffd..90a7c2a20ae6b9c7d63f1a96aa7e4a2d492d31d1 100644 --- a/doc/en/Authoring/Testing.md +++ b/doc/en/Authoring/Testing.md @@ -50,7 +50,7 @@ In this way, the teacher can record, within the question itself, how they expect On the question testing page is a "Send to CAS" button. Pressing this sends the question variables and general feedback to a special page which enables more efficient authoring of the feedback in the context of the values of the variables. You still need to copy this by hand into the question edit form when you are satisfied. -A Moodle administrator can run all of the questions tests within a particular course, or across the whole site by following the links on the STACK admin page. It is useful do to this after upgrading the STACK code on the server to identify any test cases which have changed. +A Moodle administrator can run all of the questions tests within a particular course, or across the whole site by following the links on the STACK admin page. It is useful to do this after upgrading the STACK code on the server to identify any test cases which have changed. Test cases can include a meaningful description of up to 255 characters. This field is a simple string, and is not castext. diff --git a/doc/en/CAS/Matrix.md b/doc/en/CAS/Matrix.md index 0b2e67e0412844f8eb0b8223e9ba4ce1b39f3732..763c6d5d14665d387b1f716f2a26ea17c63d306d 100644 --- a/doc/en/CAS/Matrix.md +++ b/doc/en/CAS/Matrix.md @@ -98,7 +98,7 @@ Note, STACK only displays matrices with matching parentheses. If you want somet \[ f(x) = \left\{ \begin{array}{cc} 1, & x<0 \\ 0, & x\geq 0 \end{array}\right.\] then you will have to display the matrix without parentheses and sort out the mismatching parentheses in the CASText at the level of display. -For example, if we have the question variable `f:matrix([4*x+4, x<1],[-x^2-4*x-8, x>=1];` and the castext `\[ f(x) := \left\{ {@(lmxchar:"", f)@} \right. \]` the STACK generates +For example, if we have the question variable `f:matrix([4*x+4, x<1],[-x^2-4*x-8, x>=1];` and the castext `\[ f(x) := \left\{ {@(lmxchar:"", f)@} \right. \]` STACK generates \[ f(x) := \left\{ {\begin{array}{cc} 4\cdot x+4 & x < 1 \\ -x^2-4\cdot x-8 & x\geq 1 \end{array}} \right. \] Notice the use of LaTeX `\left\{` to automatically size the parentheses and `\right.` to represent a matching, but invisible closing parentesis. diff --git a/doc/en/Developer/index.md b/doc/en/Developer/index.md index d488ff9bae492783125855b15809acca5436775b..ad3a091488ec7de458742058adc693db4ce9c9f9 100644 --- a/doc/en/Developer/index.md +++ b/doc/en/Developer/index.md @@ -18,7 +18,7 @@ If you want to track the development of STACK or report bugs then you should vis Work towards the next release of STACK is detailed on [Development track](Development_track.md). -Plans looking futher into the future are described on [Future plans](Future_plans.md). +Plans looking further into the future are described on [Future plans](Future_plans.md). The past development history is documented on [Development history](Development_history.md). @@ -32,4 +32,4 @@ There is information on [clearing the cache](Question_state_caching.md). You can also read on [adding support for Maxima packages](Maxima_packages.md). -You can read about the design of the [PHP interface to the CAS](PHP-CAS.md). \ No newline at end of file +You can read about the design of the [PHP interface to the CAS](PHP-CAS.md).