[hbss] Editorial remark - Some typos

[brunojav]

Some small typos listed below :
typos :
Line 86 :

[...] the genuine user is authorized to used the keys. [...]
to :

[...] the genuine user is authorized to use the keys. [...]

Line 95 :

[...] Secure Services Community Group as being as key to enabling a strong security and identity ecosystem.

to :

[...] Secure Services Community Group as being as key to enable a strong security and identity ecosystem.

Line 102 :

"In this document, we assume that:
to (no unexpected double quote)

In this document, we assume that:

Line 118 : add a colon at the end of the line

Line 126 : [..] One should read those use cases as attractive for in web application scenario.
>> is it a typo or an expression ("for in web scenario")

Line 153 :

[...] In some conditions, usually defined by the bank, some extra security are requested to the consumer to finalize transactions. [...]

to :

[...] In some conditions, usually defined by the bank, some extra security is requested to the consumer to finalize transactions. [...]

Line 364 : Resolve promise with signature and, if applicable, keythe public part of key used to sign.
to : Resolve promise with signature and, if applicable, key the public part of key used to sign.

Line 438 : Resolve promise with signature-nrmessage and, if applicable keythe public part of key used to sign.
to : Resolve promise with signature-nrmessage and, if applicable key the public part of key used to sign.

Line 544 :

Window interface is enhanced to expose a the hardware secure device management service.

to :

Window interface is enhanced to expose hardware secure device management service.

Line 588 :

The attribute hardwaresecuredevices represents the list of hardware secure devices presents and [...]
to :

The attribute hardwaresecuredevices represents the list of hardware secure devices present and [...]

Line 594 : UA MAY defines other classes extending the HardwareSecureDevice one representing different type of hardware secure device with specific implementation. One implementation COULD be using PKCS#11 as transport layer to communicate with a compatible hardware securedevices

to : UA MAY define other classes extending the HardwareSecureDevice one representing different types of hardware secure device with specific implementation. One implementation COULD be using PKCS#11 as transport layer to communicate with a compatible hardware secure device

Line 767 : But there is no capability to add middleware. It is up the OS manufacturer to provide support for the
to : But there is no capability to add middleware. It is up to the OS manufacturer to provide support for the

[sbahloul]

Hi Bruno

I didn't catch the following point:

Line 767 : But there is no capability to add middleware. It is up the OS manufacturer to provide support for the
to : But there is no capability to add middleware. It is up to the OS manufacturer to provide support for the