Clarify dual licensing on TLS stack

In order to avoid confusions on the TLS stack document for packages with
dual licensing such as Nettle and GMP use **or** instead of **and** to
point to the fact that only one license needs to be chosen.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

content/concepts/tls-stack.md

@@ -62,10 +62,11 @@ Whilst GnuTLS is licensed under the
 [LGPL-2.1](https://www.gnu.org/licenses/old-licenses/lgpl-2.1.en.html), it uses
 [Nettle](https://www.lysator.liu.se/~nisse/nettle/nettle.html) and
 [GMP](https://gmplib.org/). Newer versions of both of these dependencies are
-now licensed as dual GPL-2 and LGPL-3, rather than **L**GPL-2.1. 
-  
-  To avoid including GnuTLS under LGPL-3 terms, should Apertis integrate a
-newer version it would need to be utilized under the GPL-2 terms. This would
+now licensed as dual GPL-2 or LGPL-3, rather than **L**GPL-2.1.
+
+To avoid including GnuTLS under LGPL-3 terms since it is against
+[Apertis license expectations]({{< ref license-expectations.md >}}),
+Apertis would need to utilize it under the GPL-2 terms. This would
 result in the binary GnuTLS library effectively being used under the terms of
 the GPL-2 rather than LGPL-2.1. This would restrict Apertis users from using
 this Apertis provided TLS implementation either directly or indirectly from any
@@ -253,7 +254,7 @@ issues, the GnuTLS or OpenSSL may present issues for Apertis:
 [LGPL-2.1](https://www.gnu.org/licenses/old-licenses/lgpl-2.1.en.html), it uses
 [Nettle](https://www.lysator.liu.se/~nisse/nettle/nettle.html) and
 [GMP](https://gmplib.org/). Newer versions of both of these dependencies are
-now licensed as dual GPL-2 and LGPL-3, rather than **L**GPL-2.1.
+now licensed as dual GPL-2 or LGPL-3, rather than **L**GPL-2.1.
 
   To avoid including GnuTLS under LGPL-3 terms, should Apertis integrate a
 newer version it would need to be utilized under the GPL-2 terms. This would