DDSXTY13 — Typographical corrections and minor rewordings

> 2.2.2 Basic Network Inteoperability Profile

• "Interoperability"

> 7.2.3 Type Extensibility and Mutability
> [...]
> • A type may be APENDABLE,

• "APPENDABLE"

> [...]
> It is summarized more enerally in Table 12.

• "generally"

> 7.2.4.4.1 Assignability of Equivalent Types
> If two types T1 and T2 are equivalent according to the MINIMAL relation (see Section 7.3.4.7),
> then thery are mutually assignable,

• "they"

> Table 15 – Definition of the is-assignable-from relationship for primitive types
> [...]
> UINT64_TYPE
> BITMASK_TYPE if and only if
> T2.bound is between 33vand
> 64, inclusive.

• "between 33 and 64"

> Table 20 – Alternative Type Representations
> [...]
> XSD [... 2nd column]
> [...] No direct support for many of the
> contructs (e.g keys) or the types in
> the type model

• "constructs"

> 7.3.4.6.2 Hash TypeIdentifiers
> Some TypeIdentifiers include within (directly or indirectly) hashes of one of mre
> TypeObjects.
Phrase is unclear, please reword.

> 7.3.4.6.4 Indirect Hash TypeIdentifiers
> These are the HASH [...] using a hash
> TypeIdentifiers . They are distinghished byt:

• "They are distinguished by:"

> 7.4.1.1.1 Primitive types
> [...]
> • An endianness byte swap shall be performed in case the native system endianness is dif-
> ferent from the one currently configured in the XCDR stream (XCDR.cendien).

• "XCDR.cendian"

Correct the typos

Perform the typographical corrections indicated in the issue description.
Note that some of the issues indicated in the description were already resolved as part of the editorial corrections performed by OMG editors. This issue addresses the ones that were not caught in that step.