The documentation should be updated to point out that the method of forcing a replica set member to be primary has long-term consequences that are not readily apparent to someone who came to that particular page from a google search for something force Mongo primary. While it is clear in the Adjust Priority for Replica Set Member documentation, what those numbers actually mean, those replica set priority numbers seem to be used without context in the Force a Member to be Primary by Setting its Priority High of 'Force a Member to Become Primary'.

The alternative procedure Force a Member to be Primary Using Database Commands of 'Force a Member to Become Primary' does not depend on changing member priorities so should be recommended over the first procedure.