Confusing help in 'update' when using the word "merge"

The first phrase in 'bzr help update' reads:

> This will perform a merge into the working tree, and may generate conflicts.

This triggered a WTF on me, as it made me think about 'bzr merge'.

I couldn't completely understand the concept at hand until I read the 'bzr help working-trees'.

So maybe using a different word would make the issue clearer, making a difference between the "merge" among histories ('bzr merge') and the "merge" of changes into a working-tree.

This is also to say that maybe showing this link on the user guide would benefit the new users to clarify the differences on the pairs branch/checkout and pull/update (the "target types" in 'bzr help reconfigure' provided the final click to my understanding).

On the first pair, I think it should be clearly stated on the starting documentation that the concept is two-dimensional: the boundness of the branch and the "working-treeness" of the branch (but everything is a branch!)... unless I got it all wrong :)

Mental note: In fact, what would happen if I performed a merge into a branch without a working-tree? Can conflicts still arise? And how to manage them?