Replication documentation suggests current_pos instead of slave_pos

The Setting Up Replication and Global Transaction ID documents both recommend the use of current_pos.

To my knowledge, slave_pos should be used in most cases as it always refers to the latest replicated event instead of the latest processed event, the latter of which also includes events generated on the slave server. If current_pos is used instead of slave_pos, any local transactions on a slave will prevent replication from starting correctly.