Fix broken xrefs

modelica · Jul 22, 2024 · 05310bf · 05310bf
1 parent 87660da
commit 05310bf
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/index.adoc b/docs/index.adoc
@@ -131,7 +131,7 @@ The root element must contain at least one, and can contain more than one `Inter
 Each such element specifies one set of interface information for calibration using one underlying variable description file (A2L).
 Multiple elements might be provided if there are different XCP slaves embedded in the FMU, or there are other reasons why multiple A2L variable description files that apply in parallel have to be provided.
 
-Each `Interface` element has the <<following attributes,table-schema-fmi-ls-xcp-interface-attributes>>:
+Each `Interface` element has the <<table-schema-fmi-ls-xcp-interface-attributes,following attributes>>:
 
 .Interface Element Attribute Details.
 [[table-schema-fmi-ls-xcp-interface-attributes]]
@@ -183,7 +183,7 @@ The FMU must provide a valid `definition` attribute and must set at least one of
 
 Additionally the `Interface` element can contain one or more `Variable` elements, which assign relevant roles to existing FMU variables.
 
-Each `Variable` element has the <<following attributes,table-schema-fmi-ls-xcp-variable-attributes>>:
+Each `Variable` element has the <<table-schema-fmi-ls-xcp-variable-attributes,following attributes>>:
 
 .Variable Element Attribute Details.
 [[table-schema-fmi-ls-xcp-variable-attributes]]
@@ -509,7 +509,7 @@ The importer of an FMU is responsible for keeping all occurrences of the port nu
 
 Since an XCP slave is implemented inside the FMU, the FMU is responsible for starting and stopping the internal XCP service.
 
-*Using FMI 3.0*, the FMU should preferably expose its XCP configuration variables (see <<figure-xcp-configuration-parameters>>) as `structuralParameters` and start the XCP service during the first invocation of `fmi3ExitConfigurationMode` and shut it down during `fmi3Terminate`, if the FMU has no explicit power-up signal to simplify user interactions between simulator and MCD tool.
+*Using FMI 3.0*, the FMU should preferably expose its XCP configuration variables (see <<configure-external-xcp-service-settings>>) as `structuralParameters` and start the XCP service during the first invocation of `fmi3ExitConfigurationMode` and shut it down during `fmi3Terminate`, if the FMU has no explicit power-up signal to simplify user interactions between simulator and MCD tool.
 If the FMU contains a virtual ECU with power-up control (K15), all built-in OS and Basic Software services (including XCP) should follow the normal power-up protocol.
 
 If the simulator puts the FMU in `Configuration Mode` and sets the structural parameters with role `XCPService[TCP|UDP]ListenAddress` and `XCPService[TCP|UDP]Port`, the XCP slave shall use those parameters to set up the communication connection for the XCP protocol.