Well by finding that page, I know what variables I'm able to pull. Again I was able to figure it out myself but I shouldn't have had to hunt it down, and rather it should be on that initial page discussing all this.
The page in question isn't set up like your 'Core Concepts' page, which takes the time to explain everything. Again, a programmer might get it immediately, and you could argue it's an advanced topic, but I've had to communicate between PM and my own scripts often enough for it to not be a trivial addition to my toolset. I feel that page should have as much care taken as the rest of the documentation.
I could be making this a bigger issue than it is, but my gut feeling was that at first glance I had to try harder to understand and find the information I needed than the actual difficulty level of the task itself. I'm a huge proponent of instructions that spend more time explaining stuff; it's your tool and you want users to get the most out of it, so why gloss over it? Never assume the audience is going to 'get it' the way you may understand it. We've already have to deal with terrible or nonexistent Unity documentation, so a little extra time making it as simple as possible will go a long way to consumer appreciation.
Combine the two pages, make 'Accessing PlayMakerFSM in Scripts' a primary link in the sidebar or at least in Editing Basics instead of tossing it into API. Highlight each method and give an explanation and a nicely formatted example. Then list all the methods for each type, or at the very least link to the appropriate API page. As a quick example, I understand that
.Value; is the value of the variable I asked for, and that
.Value = x; is modifying it, but it's not
immediately clear for someone looking at that code for the first time, and it wasn't for me.
Well again it's not important to do any of this perhaps, as I was able to figure it out, so if not for me maybe the next guy?
Thanks Jean