From 51283daa2e58fcfd4f18f8962c1f782e1a8c35c5 Mon Sep 17 00:00:00 2001 From: Griatch Date: Thu, 3 Mar 2016 23:16:01 +0100 Subject: [PATCH] Fixed some minor typos in text. Fixed some minor formatting errors in setter/getter section. --- reference/gdscript.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/reference/gdscript.rst b/reference/gdscript.rst index c3dfb994a..c69cc1d08 100644 --- a/reference/gdscript.rst +++ b/reference/gdscript.rst @@ -861,10 +861,10 @@ It is used directly after a variable definition: var variable = value setget setterfunc, getterfunc Whenever the value of ``variable`` is modified by an *external* source -(i.e. not from local usage in the class), the *setter* function (`setterfunc`)` +(i.e. not from local usage in the class), the *setter* function (``setterfunc`` above) will be called. This happens *before* the value is changed. The *setter* must decide what to do -with the new value. Vice-versa, when ``variable`` is accessed, `getterfunc` must ``return`` -the desired value. Below is an example: +with the new value. Vice-versa, when ``variable`` is accessed, the *getter* function +(``getterfunc`` above) must ``return`` the desired value. Below is an example: :: @@ -890,7 +890,7 @@ Get/Setters are especially useful when exporting variables to editor in tool scripts or plugins, for validating input. As said *local* access will *not* trigger the setter and getter. Here is an -illustration: +illustration of this: ::