next: Methods that return booleans but take more than one arg, should not have their members flipped

[elycruz]

In the functional world its a convention to receive the returning type last; E.g., methods that create new versions of the last received value, etc.

We have some methods that are defined using the above convention however for methods that return booleans (in some places).

We should keep method args order to the non-functional convention when we're returning booleans (as this is more straight forward).

Acceptance Criteria

• List methods that need updating (to use later in release changelog).
  • instanceOf
  • hasOwnProperty
• Update methods that need updating.