Correction of changeset comment: Update the opening hours of Albert Heijn stores in the ISO3166-2 region of NL-DR

Correction of changeset comment: Fix invalid phone number related values in the ISO3166-2 region of NL-NB

Correction of changeset comment: Fix invalid phone number related values in the ISO3166-2 region of NL-LI

It also mentions here on how to map multiple phone number values osm.wiki/Key:phone#How_to_map

Though over here it also mentions that there is indeed an inconsistency going on in OSM (as always) when it comes to white space padding osm.wiki/Semi-colon_value_separator

Hi, yeah this would be an edge case that I thought it wouldn't be a big deal.

With that said, if we're using the semicolon as a delimiter, I believe it would be weird (or dirty when talking in the context of data engineering) to have a leading or trailing white space in it. As we're essentially saying that one of the phone number would be " +31 6 30898025".

I've always understood OSM as a database of geographical data for apps (etc.), rather than a final frontend for the end user. So in this context, it would be up to the data user (apps) to decided how to format it.

Changeset comment correction: Format valid phone number related values in the ISO3166-2 region of NL-GR according to the international notation of E.123