EN-301-549-Design-Principles.md

@@ -4,7 +4,7 @@ From the beginning of the work on EN 301 549, three very fundamental principles
 
 1. **In EN 301 549, requirements are written to apply to specific features and functionalities that ICT products may or may not have** (e.g. screens, keyboards, audible alerts)
 Requirements deliberately avoid referring to any specific class of product or service, as the boundaries that define what products or services belong within these product classes are usually insufficiently precise. Also, the types of functionalities that members of this product or service class may have can increase, or less commonly decrease, over time. Prior to the introduction of Smart TVs and the iPhone in 2007, the assumption would have been that requirements related to internet connectivity, apps, and wireless connection to other devices, were to either TVs or phones.
-This detachment of product features from product types has made it comparatively easy to update the EN as the scope of applicability has changed (from public procurement to Web and mobile apps). It has also meant that it has never been necessary to resort to trying to define product/service types that are referred to in the relevant legislation. ).
+This detachment of product features from product types has made it comparatively easy to update the EN as the scope of applicability has changed (from public procurement to Web and mobile apps). It has also meant that it has never been necessary to resort to trying to define product/service types that are referred to in the relevant legislation).
 Not having requirements related to specific product and service types, and not having to create our own definitions for those product and service types, should prove very beneficial as the scope of applicability expands significantly to align with the EAA.
 
 2. As stated in EN 301 549 Clause 14 "Conformance":