- What you do think about suggestion about re: the redirect. It would sort of make sense in a way but we would need to probably add something to each of the tag pages to say, available in CFSCRIPT in the following way...

I hear what you're saying. There is still confusion for some devs though.

I'm just throwing this one out there, but would it be reasonable to add some rewrite rules that would point anyone trying to access tag script urls (e.g. http://docs.lucee.org/reference/functions/[insert_tagname_here].html) to the actual equivalent tag page reference (e.g. http://docs.lucee.org/reference/tags/[insert_tagname_here].html)? I realise this might complicate matters slightly (and it may seem like overkill for such a small element within the whole CF ecosystem), but I feel it is something worth giving a bit more consideration to.

- These are not "functions" in the sense of a built-in function, they are tags in script which all follow the same convention:

[tag-name with CF] [attributes];

or

[tag-name with CF]([attributes]);

e.g.

location url="http://my.domain.com";

or

location(url="http://my.domain.com");

Personally I don't like the bracket version (introduced by Adobe and added to Railo/Lucee for compatibility), as it causes this confusion you are having. The non-bracketed version, first introduced in Railo before ACF added support for tags in script, makes this clear it is not a built-in function.

So therefore having them all "repeated" in the documentation seems a bit pointless IMHO.