SYSML14 — Part 1 of the specification

In Part 1, there is a paragraph that says, in the context of describing the origins of SysML

Currently it is common practice for systems engineers to use a wide range of modeling languages, tools, and techniques on large systems projects. In a manner similar to how UML unified the modeling languages used in the software industry, SysML is intended to unify the diverse modeling languages currently used by systems engineers.

This is not currently correct. It should be changed to.

It was then common practice for systems engineers to use a wide range of modeling languages, tools, and techniques on large systems projects. In a manner similar to how UML unified the modeling languages used in the software industry, SysML has started to unify the diverse modeling languages currently used by systems engineers.

In SysML 1.3, the time-relative reference of "Currently" in the first sentence was
removed as an editorial change, so that this sentence now begins simply, "It is
common practice ..." The sentence that follows, stating that SysML is intended to
unify diverse modeling languages, in a manner similar to UML, does not accurately
reflect the variety of ways that SysML can help integrate languages in a Model Based
Systems Engineering environment. The recently completed SysML-Modelica
Transformation Specification is an example of the use of SysML to provide a systems
engineering context for the content expressed by another language, but not to unify
the full content of such a language.
Change the text of this paragraph to indicate that the goals of SysML are both to
unify languages used by systems engineers and to support a wider range of
discipline- and domain-specific languages.