From 67175e0bdea8c522de88861437038e3d5dafc8be Mon Sep 17 00:00:00 2001 From: Andreas Junghanns Date: Tue, 14 May 2024 16:56:20 +0200 Subject: [PATCH] Improve English --- docs/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.adoc b/docs/index.adoc index 5aae799..31b1630 100644 --- a/docs/index.adoc +++ b/docs/index.adoc @@ -395,7 +395,7 @@ The configuration variables are duplicated for both transport layers, TCP and UD The FMU shall only provide the corresponding variables for the protocols it supports. Without knowing the concrete XCP slave implementation the importer cannot know if the different protocols can be used in parallel or only exclusively. -In the case the XCP service is not multi-session capable and both of the variables `org.fmi_standard.fmi_ls_xcp.EnableXcpOn[Tcp|Udp]Ip` are set to `true`, the FMU must return an error and provide a meaningful error message when exiting `Configuration Mode`. +In case the XCP service is not multi-session capable and both of the variables `org.fmi_standard.fmi_ls_xcp.EnableXcpOn[Tcp|Udp]Ip` are set to `true`, the FMU must return an error and provide a meaningful error message when exiting `Configuration Mode`. This information may also be provided in the `documentation` directory inside the FMU. The importer of an FMU is responsible for keeping all occurrences of the port number consistent, i.e., in both the FMU configuration and in the A2L file.