Difference between revisions of "Translations:Closures/15/en"

From Wazeopedia
(Importing a new version from external source)
 
(Importing a new version from external source)
 
Line 1: Line 1:
==Closures set in App==
+
=={{@|Closures set in App}}==
 
Drivers can mark an unexpected road closure while driving. Reliable requests become immediately active on the Waze map as an RTC . However, App closures are almost always defined in one-way direction with a limited duration, and they often need modification.
 
Drivers can mark an unexpected road closure while driving. Reliable requests become immediately active on the Waze map as an RTC . However, App closures are almost always defined in one-way direction with a limited duration, and they often need modification.

Latest revision as of 13:10, 9 April 2021

Information about message (contribute)
This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (Closures)
=={{@|Closures set in App}}==
Drivers can mark an unexpected road closure while driving. Reliable requests become immediately active on the Waze map as an RTC . However, App closures are almost always defined in one-way direction with a limited duration, and they often need modification.
Translation=={{@|Closures set in App}}==
Drivers can mark an unexpected road closure while driving. Reliable requests become immediately active on the Waze map as an RTC . However, App closures are almost always defined in one-way direction with a limited duration, and they often need modification.

Closures set in App link to this section

Drivers can mark an unexpected road closure while driving. Reliable requests become immediately active on the Waze map as an RTC . However, App closures are almost always defined in one-way direction with a limited duration, and they often need modification.