Does an "update-update" conflict gets created from the same node in P2P replication in MS SQL 2012?

I have been told that an update-update conflict is being created in a production environment, which is set up using p2p replication, because of concurrent update by stored procedures. The msdn reference states the update-update conflict happens only when a same row is being updated by different nodes. http://ift.tt/16H3UWo