"Intent exclusive table lock" block other page/row locks?

The web page Performance and Tuning Series: Locking and Concurrency Control - Introduction to Locking - Table Locks says that:

• an update for an "all pages locked" table first applies a "Intent exclusive table lock Update page" lock before the individual page locks.

And that page says:

• "Setting an intent lock prevents other transactions from acquiring conflicting table-level locks on the table containing the locked page."

That page seems to imply that other processes can take out page level locks, even with an "Intent exclusive table lock Update page" active.

But looking at Performance and Tuning Series: Locking and Concurrency Control - Introduction to Locking - Lock Compatibility and Lock Sufficiency, it seems to say an "exclusive intent lock" blocks all other page locks.

Does an exclusive intent table lock block other page level locks? The documents are unclear. Here's my proposed fix:

Ben Slade