Update README.md

README.md

@@ -44,17 +44,17 @@ Here are our definitions
 | Names     | Définitions                                                       | Ex of potential criticism, as classification is subjective !              |
 |-----------|------------------------------------------------------------------|-----------------------------------------------------------------------------|
 | Airspaces | This NOTAM concerns an airspace definition for restriction or for authorization (including Airway) |      
-|Communication_and_Radar|This NOTAM concerns communications (radio VHF, datalink CPDLC, ATIS, TWR,  ATS) or radar or information provided by radio or digital way such as meteo information (ex : METAR)|Why perform a discrepancy between the data (METAR) and the system which provides it (WDI) ? To avoid to merge data & system. 
+|Communication_and_Radar|This NOTAM concerns communications (radio VHF, datalink CPDLC, ATIS, TWR,  ATS) or radar or information provided by radio or digital way such as meteo information (ex : METAR)|Why separating data (METAR) and the system which provides it (WDI)? This is to prevent to merge data & system. 
 |GPS|This NOTAM concerns GPS, either for the area, either for the GPS augmentation system for landing. The procedures as GLS shall be classified as Procedure.||
-|Landing_Navaids|This NOTAM concerns landing navaids, mainly ILS (Instrument Landing System) or parts of ILS : LOC (lateral) or GLIDE (vertical), including Outer/Middle/Inner markers. This DOES NOT include the DME associated to the ILS, except if clearly explained in message (ILS, LDG, RWY).|why do not include DME ILS ? Data not obvious in message, sometimes available in Qcode, sometimes only in navaid ident
+|Landing_Navaids|This NOTAM concerns landing navaids, mainly ILS (Instrument Landing System) or parts of ILS : LOC (lateral) or GLIDE (vertical), including Outer/Middle/Inner markers. This DOES NOT include the DME associated to the ILS, except if clearly explained in message (ILS, LDG, RWY).|Why are DME and ILS not included? Data is usually not obvious in the messages: it can be retrieved sometimes through Q-code, and sometimes only from the navaid ident.
 |Obstacles|This NOTAM concerns obstacles (cranes, trees, vessels, …)||
 |Wildlife|This NOTAM concerns the wildlife issue, like birds hazard or any other animal hazard||
 |Parking|This NOTAM concerns the area where the aircrafts are parked. Usual names : apron, ramp, stand, parking. The helipads are classified as parking.||
 |Procedure|This NOTAM concerns procedures, either the standard published ones, either the specific applicable ones. If the NOTAM deals with AIP and has no obvious classification in another category, this NOTAM should be classified in this category.|
-|Runway|This NOTAM concerns runway state (closure, degraded surface, limited distance, runway arrest concern, work in progress around runway) . Runway signs and lights are NOT part of this category, except if the consequence is one of the above cases.|Why do not include everything abouta specific runway (RVRT, lights, marks...) ? To avoid to merge all in runway.
-|Services_and_Facilities|This NOTAM concerns services or facilities (fuel, meteo systems (ex : AWOS, RVR systems, windsock...), rescue, wash, pushback …), but not the signs or the lights. If the NOTAM deals with this subject and does not lead to close a precise part of the aerodrome, it should be classified in this category, rather than in another one.|Why perform a discrepancy between the data (METAR) and the system which provides it (WDI) ? To avoid to merge data & system. 
-|Signs_and_Lights|This NOTAM concerns signs or lights. If the NOTAM deals with this subject and does not lead to close a part of the aerodrome, it should be classified in this category, rather than in another one.|Why do not include everything abouta specific runway (RVRT, lights, marks...) ? To avoid to merge runway and data. 
-|Taxiway|This NOTAM concerns taxiway state or taxilane state (closure, degraded surface, work in progress around taxiway). Taxiway signs and lights are NOT part of this category, except if the consequence is one of the above cases.|Why do not include everything abouta specific runway (RVRT, lights, marks...) ? To avoid to merge all in taxiway. 
+|Runway|This NOTAM concerns runway state (closure, degraded surface, limited distance, runway arrest concern, work in progress around runway) . Runway signs and lights are NOT part of this category, except if the consequence is one of the above cases.|Why don't we include everything about a specific runway (RVRT, lights, marks...)? This would add plenty of separated information in a single class.
+|Services_and_Facilities|This NOTAM concerns services or facilities (fuel, meteo systems (ex : AWOS, RVR systems, windsock...), rescue, wash, pushback …), but not the signs or the lights. If the NOTAM deals with this subject and does not lead to close a precise part of the aerodrome, it should be classified in this category, rather than in another one.|Why separating data (METAR) and the system which provides it (WDI)? This is to prevent to merge data & system. 
+|Signs_and_Lights|This NOTAM concerns signs or lights. If the NOTAM deals with this subject and does not lead to close a part of the aerodrome, it should be classified in this category, rather than in another one.| 
+|Taxiway|This NOTAM concerns taxiway state or taxilane state (closure, degraded surface, work in progress around taxiway). Taxiway signs and lights are NOT part of this category, except if the consequence is one of the above cases.| 
 |
 
 Feel free to share your comments