From 7df55ae8b47665b2c744d709166f4f0baadefdde Mon Sep 17 00:00:00 2001 From: balaskoa <Jeno.Balasko@ericsson.com> Date: Wed, 12 Feb 2020 09:36:40 +0100 Subject: [PATCH] adoc typo Signed-off-by: balaskoa <Jeno.Balasko@ericsson.com> Change-Id: I174e95ae88dd79355b39ef96da1ab21e925c5d45 --- usrguide/referenceguide/4-ttcn3_language_extensions.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/usrguide/referenceguide/4-ttcn3_language_extensions.adoc b/usrguide/referenceguide/4-ttcn3_language_extensions.adoc index c77016f15..535b173a9 100644 --- a/usrguide/referenceguide/4-ttcn3_language_extensions.adoc +++ b/usrguide/referenceguide/4-ttcn3_language_extensions.adoc @@ -5408,7 +5408,7 @@ Unions, anytypes and ASN.1 open types are encoded as JSON objects. The object wi The following sections describe the TTCN-3 attributes that influence JSON coding (only affects TTCN-3 types, ASN.1 types cannot have attributes that influence JSON coding). -All JSON attributes begin with the word `JSON' followed by a colon (`JSON:<attribute>`). Any number of white spaces (spaces and tabs only) can be added between each word or identifier in the attribute syntax, but at least one is necessary if the syntax does not specify a separator (a comma or a colon). The attribute can also start and end with white spaces. +All JSON attributes begin with the word `JSON` followed by a colon (`JSON:<attribute>`). Any number of white spaces (spaces and tabs only) can be added between each word or identifier in the attribute syntax, but at least one is necessary if the syntax does not specify a separator (a comma or a colon). The attribute can also start and end with white spaces. Alternatively the syntaxes defined in <<13-references.adoc#_25, [25]>> can also be used, for the supported attributes (without the need for the `JSON`: prefix). -- GitLab