There are three locations in the built-in documentation (as of 3.61a) where
"insure" is incorrectly used instead of "ensure":


[3.1.2.8.4 - immediately before the second yellow box]

The default amount of 1.0 is the maximum jitter which will insure that all
super-samples remain inside the original pixel.


[3.2.2.3.3 - at the end of the paragraph following the first blue box]

Type checking is performed to insure that the proper type data is read into
these identifiers.


[3.2.2.6.4 - at the end of second yellow box]

It is up to the user to insure that something inside the loop changes so
that it eventually terminates.


Bent

Post a reply to this message