From 3abad718671109c26d03cd16e94333f7928a561c Mon Sep 17 00:00:00 2001 From: "Reynaldo H. Verdejo Pinochet" Date: Mon, 14 Oct 2013 18:34:06 -0700 Subject: [PATCH] docs: Gram and nit fixes for part-controller.txt --- docs/design/part-controller.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/design/part-controller.txt b/docs/design/part-controller.txt index 9476092714..b5c9393836 100644 --- a/docs/design/part-controller.txt +++ b/docs/design/part-controller.txt @@ -14,7 +14,7 @@ Elements don't need to do much. They need to: before accessing the parameters. All ordered property types can be automated (int, double, boolean, enum). Other -property types can be automates as well by using special control bindings. One can +property types can also be automated by using special control bindings. One can e.g. write a control-binding that updates a text property based on timestamps. Application view @@ -52,8 +52,8 @@ control-source value ranges ranged-control-binding - it might be a nice thing to have a control-binding that has scale and offset properties -- when attaching a contro-source to e.g. volume one needs to be aware that the values - go from [0.0 to 4.0] +- when attaching a control-source to e.g. volume, one needs to be aware that + the values go from [0.0 to 4.0] - we can also have a "mapping-mode"={AS_IS, TRANSFORMED} on direct-control-binding and two extra properties that are used in TRANSFORMED mode