no-dom-traversal-in-attributechangedcallback.md states:

It is instead preferable to move such DOM traversals away from attributeChangedCallback, using one of the following:

• move traversals to connectedCallback

This seems to conflict with no-dom-traversal-in-connectedcallback.md which states Traversing the DOM during the connectedCallback phase is error-prone, which confuses me. it would be helpful to clarify this.