the special characters are now set back to their initial form (to correct a character coding error)

Signed-off-by: Kristof Szabados <Kristof.Szabados@ericsson.com>

org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/3-setting_workbench_preferences.adoc

@@ -6,7 +6,7 @@ This section gives an overview about the various settings related to the workben
 
 In Eclipse, workbench preferences are used to set user specific general rules, which apply to every project; for example, preferred font styles, access to version handling systems and so on.
 
-Workbench preferences are accessible selecting *Window / Preferences*. Clicking on the menu item will bring up the preferences page. The opening window contains a preference tree on the left pane to ease navigation – see Figure 8.
+Workbench preferences are accessible selecting *Window / Preferences*. Clicking on the menu item will bring up the preferences page. The opening window contains a preference tree on the left pane to ease navigation – see Figure 8.
 
 image::images/2_F8.png[title="TITAN preferences sub-tree"]
 
@@ -39,13 +39,13 @@ The option is NOT CHECKED by default.
 
 * **When on-the-fly analysis ends the compiler markers.**
 +
-When the on-the-fly analyzer starts it can trigger the following behaviors for error markers generated by the compiler previously: *“Stay unchanged�*, *“Become outdated�*, and *“Are removed�*. +
-The default setting is: *“Become outdated�*
+When the on-the-fly analyzer starts it can trigger the following behaviors for error markers generated by the compiler previously: *“Stay unchanged”*, *“Become outdated”*, and *“Are removed”*. +
+The default setting is: *“Become outdated”*
 
 * **When the compiler runs the on-the-fly markers.**
 +
-When the compiler starts it can trigger the following behaviors for error markers generated by the on-the-fly analyzer previously: *“Are removed�*, *“Stay�*.Setting this option to *“Stay�* can enhance the speed of the on-the-fly analyzer, because if the markers need to be refreshed, so does all syntactic and semantic information needs to be refreshed too. +
-The default setting is: *“Are removed�.*
+When the compiler starts it can trigger the following behaviors for error markers generated by the on-the-fly analyzer previously: *“Are removed”*, *“Stay”*.Setting this option to *“Stay”* can enhance the speed of the on-the-fly analyzer, because if the markers need to be refreshed, so does all syntactic and semantic information needs to be refreshed too. +
+The default setting is: *“Are removed”.*
 
 * **Maximum number of build processes to use.**
 +
@@ -54,7 +54,7 @@ The option is set equal the number of processors/cores available in the system b
 
 * **Display debug preferences**
 +
-By default, the Designer plug-in isn’t logging debug information to the Debug Console to help solving problems.However as errors are reported to the Error Log of Eclipse this information is rarely used. Most of the time these printouts hold no value for the users.Debugging and load balancing features can be set by this option see <<debug, here>>.
+By default, the Designer plug-in isn’t logging debug information to the Debug Console to help solving problems.However as errors are reported to the Error Log of Eclipse this information is rarely used. Most of the time these printouts hold no value for the users.Debugging and load balancing features can be set by this option see <<debug, here>>.
 +
 The option is NOT CHECKED by default because most of the time these features hold no value for the users.
 +
@@ -197,7 +197,7 @@ By default we do not include any information on any option/setting in the descri
 
 * **Pack all data of related projects:**
 +
-Project references in Eclipse are a great way to structure one’s work into manageable pieces. However, if one of those projects is not available, building the whole set is not possible. For this reason, it is possible to save all information from all required projects into one project descriptor. Its default value is off.
+Project references in Eclipse are a great way to structure one’s work into manageable pieces. However, if one of those projects is not available, building the whole set is not possible. For this reason, it is possible to save all information from all required projects into one project descriptor. Its default value is off.
 
 The second group contains the settings for automatic export.
 
@@ -549,4 +549,3 @@ The first group deals with automatic bracket insertion. For the last three items
 The second group contains only one box for controlling new line insertion. A checked box has the following effect: if the user hits *Enter* between two curly brackets, the cursor will be moved to the next line and the closing bracket even further, to the second line. This way an empty line is formed with an opening bracket above and a closing bracket below it. The cursor will be placed on the empty line.
 
 By default, all boxes are checked.
-

org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/4-managing_projects.adoc

@@ -72,7 +72,7 @@ There are two ways to add files to a project. The first one, using wizards, is t
 [[using-wizards-to-add-files-to-the-project]]
 === Using Wizards to Add Files to the Project
 
-Wizards are available to create some of the TITAN modules footnote:[The terms "modules" and "files" are used interchangeably in this section.] (TTCN-3, ASN.1 and Configuration files). This functionality is reached by selecting *File / New* (see Figure 26 above).
+Wizards are available to create some of the TITAN modulesfootnote:[The terms "modules" and "files" are used interchangeably in this section.] (TTCN-3, ASN.1 and Configuration files). This functionality is reached by selecting *File / New* (see Figure 26 above).
 
 In the Project Explorer view, the wizards "TTCN-3 Module", "ASN.1 Module" and "Configuration file" can be reached by **right click**ing the content area and selecting *New / Other…* .
 
@@ -141,13 +141,13 @@ image::images/4_F36.png[title="Manage configurations"]
 On this window it is possible to create new configurations, delete existing ones, or simply rename one.
 
 [NOTE]
-=====
+====
 Even though the settings of the Default configuration can be changed it cannot be deleted or renamed, the existence of this configuration is needed to be forward compatible with older versions of our tools.
 
 [.underline]#The build configuration name cannot contain whitespace character.#
 
 [.underline]#The visible build configuration settings always refer to the active build configuration.# To change a build configuration at first it shall be selected as active configuration, then some of the settings described below shall be modified then the settings shall be saved by pushing the button "Apply" or "OK".
-=====
+====
 
 [[setting-the-local-build-properties-of-a-project]]
 === Setting the Local Build Properties of a Project
@@ -823,11 +823,11 @@ ttcn3_makefilegen -V -P /home/ethbaat/DiameterApplib/Diameter_Applib_2013_03_01
 ....
 
 [NOTE]
-=====
+====
 The compressed file will contain the files in the same structure as they have been stored in the source root directory.
 
 See more information about the command ttcn3_makefilegen in sections 6.1.2 and 6.1.3 in TITAN Programmer’s Technical Reference for TITAN TTCN-3 Test Executor <<12-references.adoc#_4, [4]>>.
-=====
+====
 
 == Formatting Log Files
 

org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/7-editing_with_titan_designer_plugin.adoc

@@ -143,7 +143,7 @@ To define macros outside of files the Eclipse TITAN plug-in uses the settings gi
 
 [width="100%",cols="m,",,]
 |===
-|#define MACRO_NAME <expression> |Define a macro, it’s value is the value of the integer expression
+|#define MACRO_NAME <expression> |Define a macro, it’s value is the value of the integer expression
 |#undef MACRO_NAME |Delete a macro
 |#ifdef MACRO_NAME |The code in this branch is active if the macro `MACRO_NAME` was defined previously
 |#ifndef MACRO_NAME |The code in this branch is inactive if the macro `MACRO_NAME` was defined previously
@@ -164,7 +164,7 @@ NOTE: ttcnpp files are not analyzed incrementally even if incremental analysis i
 
 === Limitations
 
-The on-the-fly parser does not support the single line comment in ASN.1 files when placed right after non-comment elements. A simple workaround for this problem is to insert a SPACE character between the last non-comment character and the "`—`" sign.
+The on-the-fly parser does not support the single line comment in ASN.1 files when placed right after non-comment elements. A simple workaround for this problem is to insert a SPACE character between the last non-comment character and the "`—`" sign.
 
 Limitations of preprocessing:
 
@@ -237,7 +237,7 @@ The highest level of content assistance is available for TTCN-3 and ASN.1 files.
 . From the smallest scope found the scope hierarchy is traversed in a bottom-up manner to find the possible definitions. (The definitions imported are checked after the definitions of the actual module).
 . When a relevant definition is found the search for possible proposals continues inside its structure. For example, if the definition is a variable of a structured type, the reference is used to detect the subtypes or fields that the reference could point to if it were to be completed that way.
 
-The proposals are ordered in the following way (definitions don’t hide each other in the proposal list):
+The proposals are ordered in the following way (definitions don’t hide each other in the proposal list):
 
 . Dynamic elements available in the given scope. The elements are ordered by the distance of the element definition from the completion point in the scope hierarchy. For example, a local variable will always precede module definitions. The definitions that are most likely to be used are placed earlier in the list. If there is more than one proposal from the same scope, they are ordered alphabetically.
 . Skeletons available in the given scope. The skeletons are ordered alphabetically.
@@ -245,7 +245,7 @@ The proposals are ordered in the following way (definitions don’t hide ea
 
 === Content Assistance Limitations
 
-Full context sensitivity is not possible yet. Only the scopes and the type structures are used to filter the list of proposals. For this reason, the content assistant might offer completion proposals, which are possible in the actual scope but not in the actual context. It is the user’s task to choose the right proposal.
+Full context sensitivity is not possible yet. Only the scopes and the type structures are used to filter the list of proposals. For this reason, the content assistant might offer completion proposals, which are possible in the actual scope but not in the actual context. It is the user’s task to choose the right proposal.
 
 Only data gathered and stored by the on-the-fly parsers can be offered. If this data is outdated or not complete, the content assistance will also offer outdated or limited information. Section 3.1 explains how this can happen.
 
@@ -274,7 +274,7 @@ Open Declaration works for TTCN-3 and ASN.1 modules and configuration files. For
 
 Open configuration files listed in the include section. If the selected configuration file cannot be found the error is reported in the *TITAN Debug Console* and *the status line of Eclipse*.
 
-Find module parameter declarations. If the module parameter is given as a module specific module parameter (e.g. `module.parameter`) only the given module is searched through for the declaration. Otherwise (e.g. `.parameter` or `parameter`) all modules of the project are taken into account. Duplicate module parameter declarations and errors are reported in the same way as for macro definitions.
+Find module parameter declarations. If the module parameter is given as a module specific module parameter (e.g. `module.parameter`) only the given module is searched through for the declaration. Otherwise (e.g. `.parameter` or `parameter`) all modules of the project are taken into account. Duplicate module parameter declarations and errors are reported in the same way as for macro definitions.
 
 [[find-references]]
 == Find References
@@ -297,7 +297,7 @@ type record MyRec {
 ...
 var MyRec v_myrec;
 ...
-v_myrec.rec.rec.rec.str := “foo�;
+v_myrec.rec.rec.rec.str := “foo”;
 ----
 
 Searching for field rec will give 3 hits in the above line, because the reference `v_myrec.rec.rec.rec.str` contains the identifier of the rec field 3 times.
@@ -370,9 +370,9 @@ The graphical pages are explained in detail in the sections below.
 
 === Module Parameters Section
 
-On this page (new) values can be assigned to parameters defined in the TTCN–3 modules.
+On this page (new) values can be assigned to parameters defined in the TTCN–3 modules.
 
-A new parameter can be added by clicking the *Add…* button. The column *Module name* contains the name of the module where the parameter is used. The parameter can be used in all modules when this column is left blank or filled with an asterisk. The column *Module parameter name* is self-explanatory. The value of the parameter is determined by the string in the pane *Module parameter details* in free form as parameters may have different formats.
+A new parameter can be added by clicking the *Add…* button. The column *Module name* contains the name of the module where the parameter is used. The parameter can be used in all modules when this column is left blank or filled with an asterisk. The column *Module parameter name* is self-explanatory. The value of the parameter is determined by the string in the pane *Module parameter details* in free form as parameters may have different formats.
 
 Highlighted existing parameters are removed by clicking the *Remove* button.
 
@@ -386,7 +386,7 @@ Changes made to the parameters must be saved by the shortcut key *Ctrl+S*.
 
 The values of all parameters on this page are passed to test ports.
 
-A new parameter can be added by clicking the *Add…* button. The column *Component name* contains the name of the component defining the test port. An asterisk (*) denotes all ports of the Test System Interface. The column *Test port name* is the name of the test port. The column *Parameter name* is self-explanatory. The value of the parameter is determined by the string in the pane *Test port parameter details* in free form as parameters may have different formats.
+A new parameter can be added by clicking the *Add…* button. The column *Component name* contains the name of the component defining the test port. An asterisk (*) denotes all ports of the Test System Interface. The column *Test port name* is the name of the test port. The column *Parameter name* is self-explanatory. The value of the parameter is determined by the string in the pane *Test port parameter details* in free form as parameters may have different formats.
 
 Highlighted existing parameters are removed by clicking the *Remove* button.
 
@@ -420,7 +420,7 @@ The *Use of unix domain socket communication* field can turn on or off the usage
 
 The aim of the *Components* table is to restrict component execution to certain (group of) hosts. These constraints are useful when distributed tests are executed in a heterogeneous environment. The participating computers may have different hardware setup, computing capacity or operating system.
 
-A new restriction is added by clicking the *Add…* button to the right of the first table. The column *Component name* contains component to be restricted. The column *Host name* contains either a host name, a group of hosts (see <<group-section, here>>) or an IP address of a host.
+A new restriction is added by clicking the *Add…* button to the right of the first table. The column *Component name* contains component to be restricted. The column *Host name* contains either a host name, a group of hosts (see <<group-section, here>>) or an IP address of a host.
 
 Highlighted components are removed by the button *Remove*.
 
@@ -461,7 +461,7 @@ The field *End testcase* contains the path to the shell script executed after a
 
 This table points out parts of the test suite to be executed. Only test cases having no parameters can be executed from this section.
 
-A new test case is added by clicking the *Add…* button to the right of the table. The column *Module name* contains the name of the module where the test case is defined. The column *Testcase…* lists the test cases to be executed. An asterisk (*) denotes that all test cases in the given module must be executed.
+A new test case is added by clicking the *Add…* button to the right of the table. The column *Module name* contains the name of the module where the test case is defined. The column *Testcase…* lists the test cases to be executed. An asterisk (*) denotes that all test cases in the given module must be executed.
 
 Highlighted test cases are removed by the button *Remove*.
 
@@ -479,7 +479,7 @@ Changes made to the parameters must be saved by the shortcut key *Ctrl + S*.
 
 This table lists the configuration files to be imported. This way there is no need to merge configuration files when parameter definitions needed are dispersed over several files.
 
-A new configuration file is imported by clicking the *Add…* button to the right of the upper table. The column *File name* contains between quotation marks the name of the files to be imported.
+A new configuration file is imported by clicking the *Add…* button to the right of the upper table. The column *File name* contains between quotation marks the name of the files to be imported.
 
 Highlighted files are removed by the button *Remove*.
 
@@ -489,7 +489,7 @@ The field *Total* under the buttons shows the number of the imported files.
 
 This table contains macro definitions that can be used in other configuration file sections.
 
-A new macro definition is added by clicking the *Add…* button to the right of the lower table. The column *Definition* contains the macro name whereas the column *Definition value* contains the macro itself between quotation marks.
+A new macro definition is added by clicking the *Add…* button to the right of the lower table. The column *Definition* contains the macro name whereas the column *Definition value* contains the macro itself between quotation marks.
 
 Highlighted macros are removed by the button *Remove*.
 
@@ -506,7 +506,7 @@ image::images/7_F101.jpg[title="Figure Logging"]
 
 In the components and plug-ins section a tree of components and plug-ins can be created and managed.
 
-On the first level of the tree components can be added using the _Add component…_ button.Using the _Add plug-in…_ button plug-ins can be added under each component on the second level of the tree.
+On the first level of the tree components can be added using the _Add component…_ button.Using the _Add plug-in…_ button plug-ins can be added under each component on the second level of the tree.
 
 Both component and plug-in names must be valid identifiers. The only exception is the "\*" component, this can be used to specify settings which are applied to all components and plug-ins.The "*" plug-in is automatically inserted; this can be used to specify settings which are applied to all plug-ins of the selected component. To specify settings for a specific component and plug-in one of the tree elements must be selected.
 
@@ -525,15 +525,15 @@ Any component or plug-in can be deleted using the _Remove selected_ button.
 
 `Seconds` results relative timestamps in format `s.microsec.`
 
-*SourceInfoFormat* controls the appearance of the test event location information (position in the TTCN–3 source code). The option can take one of the three possible values: `None`, `Single` and `Stack`. If set to `Single`, the location information of the TTCN–3 statement is logged that is currently being executed. When `Stack` is used, the entire TTCN–3 call stack is logged. The value `None` disables the printing of location information.
+*SourceInfoFormat* controls the appearance of the test event location information (position in the TTCN–3 source code). The option can take one of the three possible values: `None`, `Single` and `Stack`. If set to `Single`, the location information of the TTCN–3 statement is logged that is currently being executed. When `Stack` is used, the entire TTCN–3 call stack is logged. The value `None` disables the printing of location information.
 
-*AppendFile* controls whether the run-time environment shall keep the contents of existing log files when starting execution. The possible values are `Yes` or `No`. The default is No, which means that all events from the previous test execution will be overwritten.
+*AppendFile* controls whether the run-time environment shall keep the contents of existing log files when starting execution. The possible values are `Yes` or `No`. The default is No, which means that all events from the previous test execution will be overwritten.
 
 *LogEventTypes* can be useful for log post-filtering scripts. The possible values are `Yes`, `No`, `Detailed` and `Subcategories`. These values are explained in the section `LogEventTypes` of <<12-references.adoc#_4, [4]>>.
 
-*LogEntityName:* if set to `Yes`, the name of the TTCN–3 entity is indicated in the log file along with the file name and line number.
+*LogEntityName:* if set to `Yes`, the name of the TTCN–3 entity is indicated in the log file along with the file name and line number.
 
-*MatchingHints:* controls the verbosity of the logger regarding to template matching. The possible values are `Compact` and `Detailed`. The default is `Compact`, which shows the matched/unmatched fields of messages in a dot-separated notation. The Detailed version is similar to the former logging format. It’s more verbose and preserves the message structures.
+*MatchingHints:* controls the verbosity of the logger regarding to template matching. The possible values are `Compact` and `Detailed`. The default is `Compact`, which shows the matched/unmatched fields of messages in a dot-separated notation. The Detailed version is similar to the former logging format. It’s more verbose and preserves the message structures.
 
 *Log file size* limits log file growth: when the file reaches the limit given in kilobytes, the log file is closed and a new one is opened with a different name. The naming scheme is explained in the section `LogFileSize` of <<12-references.adoc#_4, [4]>>.
 
@@ -556,4 +556,3 @@ Any component or plug-in can be deleted using the _Remove selected_ button.
 === Limitations on the Graphical Pages
 
 The entered parameter values are not verified: any character string can be entered in any field.
-

org.eclipse.titan.help/docs/Eclipse_installationguide/Eclipse_installationguide.adoc

@@ -64,7 +64,7 @@ This document uses the following typographical conventions:
 
 * ANTLR Runtime 4.3
 
-* TITAN TTCN–3 Toolset installed. (Only needed if Eclipse is used for project compilation and test execution. Editing does not require it.)
+* TITAN TTCN–3 Toolset installed. (Only needed if Eclipse is used for project compilation and test execution. Editing does not require it.)
 
 * J2SE(TM) Runtime Environment 6.0 or later installed and set in Eclipse as the Java Runtime Environment
 
@@ -103,7 +103,7 @@ For example, if the cygwin root is "C:64" then "Path" should contain "C:64\cygwi
 = Installing prerequisites
 
 [[installing-the-titan-ttcn-3-toolset]]
-== Installing the TITAN TTCN–3 Toolset
+== Installing the TITAN TTCN–3 Toolset
 
 For detailed information on installing the TITAN TTCN-3 Toolset, and configuring the environment variables for TITAN to work, refer to <<_1, Installation Guide for TITAN TTCN-3 Test Executor>>.
 
@@ -234,7 +234,7 @@ If Java 1.8 is used then `MaxPermSize` is ignored, its support is removed. Use t
 -Xmx4g
 ----
 
-NOTE: If you cannot edit the `eclipse.ini` file, you can start eclipse with flags. For example `eclipse –vmargs -Xmx4g` modifies the maximum memory allocation for the virtual machine.
+NOTE: If you cannot edit the `eclipse.ini` file, you can start eclipse with flags. For example `eclipse –vmargs -Xmx4g` modifies the maximum memory allocation for the virtual machine.
 
 = Compatibility Issues
 

org.eclipse.titanium.refactoring/docs/Titanium_Refactoring_Description/Titanium_Refactoring_Description.adoc

@@ -45,15 +45,15 @@ This description contains detailed information on using the TitaniumRefactoring
 The TitaniumRefactoring tool is an Eclipse plug-in, extending the TITAN Designer for the Eclipse IDE Toolset with refactoring functionality. The Designer is required to be installed and be present for the correct operation.
 
 [[the-titan-implementation-of-ttcn-3]]
-== The TITAN implementation of TTCN–3
+== The TITAN implementation of TTCN–3
 
-The TitaniumRefactoring plug-in is extending the TITAN Designer plug-in, which is an implementation of TTCN–3 Core Language standard (<<_3, [3]>>), supporting of ASN.1 language (<<_4, [4]>>).
+The TitaniumRefactoring plug-in is extending the TITAN Designer plug-in, which is an implementation of TTCN–3 Core Language standard (<<_3, [3]>>), supporting of ASN.1 language (<<_4, [4]>>).
 
-The limitations present in the Designer plug-in also apply here: there are TTCN–3 language constructs which are not yet supported in the current version, while there are also some non-standard extensions implemented by TITAN. Information on these limitations and extensions and also some clarifications of how the standard has been implemented in TITAN, can be found in the <<_2, TITAN Programmer’s Technical Reference>>.
+The limitations present in the Designer plug-in also apply here: there are TTCN–3 language constructs which are not yet supported in the current version, while there are also some non-standard extensions implemented by TITAN. Information on these limitations and extensions and also some clarifications of how the standard has been implemented in TITAN, can be found in the <<_2, TITAN Programmer’s Technical Reference>>.
 
 == Intended audience
 
-This document is intended for users of the TITAN TTCN–3 Test Toolset (product number: CRL 113 200/1).
+This document is intended for users of the TITAN TTCN–3 Test Toolset (product number: CRL 113 200/1).
 
 == Presumed knowledge
 
@@ -232,9 +232,9 @@ The algorithm searches for whole statements in the selection, half selected stat
 
 If the selection is valid for the operation, then a wizard is presented for the user to specify the name of the new function and the names of its parameters. After this, the produced changes can be reviewed and accepted by clicking on the *Finish* button.
 
-image::images/6_F6.png[title="Extract to function wizard – specify new function name"]
+image::images/6_F6.png[title="Extract to function wizard – specify new function name"]
 
-image::images/6_F7.png[title="Extract to function wizard – specify parameter names"]
+image::images/6_F7.png[title="Extract to function wizard – specify parameter names"]
 
 == Known limitations
 
@@ -266,7 +266,7 @@ The algorithm searches for log statements in the selection and modifies them if
 
 After selecting the appropriate options, click on the *OK* button to finish the operation.
 
-image::images/8_F8.png[title="Add context info wizard – modify settings"]
+image::images/8_F8.png[title="Add context info wizard – modify settings"]
 
 === Settings
 
@@ -318,7 +318,7 @@ To run the refactoring operation on a specific TTCN function, move the cursor in
 
 After selecting the appropriate options, click on the *OK* button to finish the operation, or use the *Preview* action to browse the changes before accepting them.
 
-image::images/10_F10.png[title="Minimize scope wizard – modify settings"]
+image::images/10_F10.png[title="Minimize scope wizard – modify settings"]
 
 === Settings
 
@@ -372,7 +372,7 @@ Please note that the "Lazy-fication of formal parameters" feature is working onl
 * [3] link:http://www.etsi.org/deliver/etsi_es/201800_201899/20187301/04.01.01_60/es_20187301v040101p.pdf[Methods for Testing and Specification (MTS);The Testing and Test Control Notation version 3.Part 1: Core Language European Telecommunications Standards Institute. ES 201 873-1 Version 4.1.1, July 2009]
 
 [[_4]]
-* [4] link:http://www.etsi.org/deliver/etsi_es/201800_201899/20187307/04.01.01_60/es_20187307v040101p.pdf[Methods for Testing and Specification (MTS);The Testing and Test Control Notation version 3.Part 7: Using ASN.1 with TTCN–3 European Telecommunications Standards Institute. ES 201 873-7 Version 4.1.1, July 2009]
+* [4] link:http://www.etsi.org/deliver/etsi_es/201800_201899/20187307/04.01.01_60/es_20187307v040101p.pdf[Methods for Testing and Specification (MTS);The Testing and Test Control Notation version 3.Part 7: Using ASN.1 with TTCN–3 European Telecommunications Standards Institute. ES 201 873-7 Version 4.1.1, July 2009]
 
 = Glossary
 
@@ -380,4 +380,4 @@ ASN.1:: Abstract Syntax Notation One
 
 IDE:: Integrated Development Environment
 
-TTCN–3:: Tree and Tabular Combined Notation version 3 (formerly)Testing and Test Control Notation (new resolution)
+TTCN–3:: Tree and Tabular Combined Notation version 3 (formerly)Testing and Test Control Notation (new resolution)

org.eclipse.titanium/docs/Titanium_referenceguide/Titanium_referenceguide.adoc

@@ -42,7 +42,7 @@ The purpose of this document is to provide detailed information on writing compo
 
 == Target Groups
 
-This document is intended for programmers of TTCN–3 test suites with information in addition to that provided in the TITAN User Guide <<_3, [3]>>. It is recommended that the programmer reads the TITAN User Guide before reading this document.
+This document is intended for programmers of TTCN–3 test suites with information in addition to that provided in the TITAN User Guide <<_3, [3]>>. It is recommended that the programmer reads the TITAN User Guide before reading this document.
 
 == Typographical Conventions
 
@@ -320,7 +320,7 @@ The last, important step is to refresh the documentation. In the chapter Titaniu
 
 Example:
 
-In docs/Titanium – 1551
+In docs/Titanium – 1551
 
 Titanium Preferences / Code Smell Preferences / Potential structural problems
 
@@ -582,16 +582,16 @@ The *`.xls`* format used by the *`jxl`* library only supports 255 columns in a t
 
 
 [[_6]]
-* [6] TTCN–3 Style Guide
+* [6] TTCN–3 Style Guide
 
 [[_7]]
-* [7] TTCN–3 Naming Convention
+* [7] TTCN–3 Naming Convention
 
 [[_8]]
 * [8] link:https://www.etsi.org/deliver/etsi_es/201800_201899/20187310/04.05.01_60/es_20187310v040501p.pdf[Methods for Testing and Specification (MTS);The Testing and Test Control Notation version 3.Part 1: Core Language European Telecommunications Standards Institute. ES 201 873-1 Version 4.5.1, April 2013]
 
 [[_9]]
-* [9] link:https://www.etsi.org/deliver/etsi_es/201800_201899/20187304/04.04.01_60/es_20187304v040401p.pdf[Methods for Testing and Specification (MTS);The Testing and Test Control Notation version 3.Part 4: TTCN–3 Operational Semantics European Telecommunications Standards Institute. ES 201 873-4 Version 4.4.1, April 2012]
+* [9] link:https://www.etsi.org/deliver/etsi_es/201800_201899/20187304/04.04.01_60/es_20187304v040401p.pdf[Methods for Testing and Specification (MTS);The Testing and Test Control Notation version 3.Part 4: TTCN–3 Operational Semantics European Telecommunications Standards Institute. ES 201 873-4 Version 4.4.1, April 2012]
 
 [[_10]]
-* [10] link:https://www.etsi.org/deliver/etsi_es/201800_201899/20187307/04.05.01_60/es_20187307v040501p.pdf[Methods for Testing and Specification (MTS);The Testing and Test Control Notation version 3.Part 7: Using ASN.1 with TTCN–3 European Telecommunications Standards Institute. ES 201 873-7 Version 4.5.1, April 2013]
+* [10] link:https://www.etsi.org/deliver/etsi_es/201800_201899/20187307/04.05.01_60/es_20187307v040501p.pdf[Methods for Testing and Specification (MTS);The Testing and Test Control Notation version 3.Part 7: Using ASN.1 with TTCN–3 European Telecommunications Standards Institute. ES 201 873-7 Version 4.5.1, April 2013]