KamasamaK

I will remove the `returns` from tag docs based on the feedback. Another issue I've come across is whether the `default` and `values` items in `params` should match the param's...

An `engines` object would be good for this, but it would need to relate to each parameter instead of the entity as a whole. Also, @shaedrich brings up a good...

I did find that it supports `deprecated` and `removed` when looking at the code (I initially had named them `deprecated_version` and `removed_version` to match `minimum_version`), but missed them previously since...

I feel like this would only work well if we had something like the `member_details` property I proposed in [this comment](https://github.com/foundeo/cfdocs/issues/525#issuecomment-327285363) where you could use `type`.`name` as the target.

Interesting. Adding new types, especially undocumented, seems like it could break backward compatibility in some cases. I'm guessing these would take precedence over components of the same name, though I...

I see there's a ticket for Lucee, but I would recommend opening a [ticket with Adobe](https://tracker.adobe.com) to have these documented. As for whether they add them to typed arrays, that...

I've started this and I've found there to be more discrepancies than I expected. Also, there are discrepancies between the PDF and the web docs, so I'm siding with the...

@shawnoden You are correct that I've only done up to C. I've been meaning to get back to this, but I have not done any after C that are pending....

The square brackets seems to be the preferred way to denote this, but the `required` value in `params` is most important. We could even dynamically generate the syntax string with...

See #883 for discussion on formatting descriptions. This issue is just about changing parameter names.