Usage of old-style validation macros is discouraged, the new validates macro is the way to go.
Documentation has the implicit goal of showing the recommended idioms by putting emphasis and obviating some valid but not-recommended stuff in examples across the docs.
With all that in mind, since the old-style macros are not formally deprecated, you could put a short new section as the last one related to validations saying that there are some old-style macros, linking to the API (rather than expanding them in the guide), and saying that their usage is discouraged nowadays.
Alternatively the guide could remain as it is, since old-style validation macros are there because of backwards compatibility mostly. It is OK that they appear in the API, but top-down docs like guides do not need to be exhaustive in that sense, they better explain how things are done today.