Context Navigation

Changes between Initial Version and Version 1 of Ticket #11564

-              initial
+              v1
 This would be helpful in case a user opens up an area and does a validation on that area.  Since {{{oneway=no}}} is required on a {{{motorway}}}/{{{motorway_link}}} segment that's two ways (non-reversible), not having that tag could cause routing errors and it would be nice to be alerted to said way via 'Other' so it could be double checked.
+This would be helpful in case a user opens up an area and does a validation on that area.
 Since normally you don't find the two-way ways for both types, that's why I suggested mentioning about the way lacking the oneway tag in the 'Other' part since it could point out the possible error mentioned above which breaks routing.  Some people might not be aware of the requirement for {{{oneway=no}}} on them since all other highway ways don't require it for two-way traffic.
+Since {{{oneway=no}}} is required on a {{{motorway}}}/{{{motorway_link}}} segment that's two-way traffic (not {{{oneway=reversible}}}, which is required if reversible no matter what on any way), not having that tag could cause routing errors and it would be nice to be alerted to said way via 'Other' so it could be double checked.  Some people might not be aware of the requirement for {{{oneway=no}}} on them since all other highway ways don't require it for two-way traffic, and thus, leave it un-tagged.
 {{{