fix arg ordering for balanceOf in Split-Id section (#5717)

Co-authored-by: Sam Wilson <[email protected]>

EIPS/eip-1155.md

@@ -669,9 +669,9 @@ uint128 indexNFT = 50;
 
 uint256 baseTokenFT = 54321 << 128;
 
-balanceOf(baseTokenNFT, msg.sender); // Get balance of the base token for non-fungible set 12345 (this MAY be used to get balance of the user for all of this token set if the implementation wishes as a convenience).
-balanceOf(baseTokenNFT + indexNFT, msg.sender); // Get balance of the token at index 50 for non-fungible set 12345 (should be 1 if user owns the individual non-fungible token or 0 if they do not).
-balanceOf(baseTokenFT, msg.sender); // Get balance of the fungible base token 54321.
+balanceOf(msg.sender, baseTokenNFT); // Get balance of the base token for non-fungible set 12345 (this MAY be used to get balance of the user for all of this token set if the implementation wishes as a convenience).
+balanceOf(msg.sender, baseTokenNFT + indexNFT); // Get balance of the token at index 50 for non-fungible set 12345 (should be 1 if user owns the individual non-fungible token or 0 if they do not).
+balanceOf(msg.sender, baseTokenFT); // Get balance of the fungible base token 54321.
 ```
 
 Note that 128 is an arbitrary number, an implementation MAY choose how they would like this split to occur as suitable for their use case. An observer of the contract would simply see events showing balance transfers and mints happening and MAY track the balances using that information alone.