From 07e05b4c55c0a179e5a62e4aa7af67ca4e6e8cb5 Mon Sep 17 00:00:00 2001 From: Yuval Tassa Date: Mon, 11 Dec 2023 08:41:07 -0800 Subject: [PATCH] Fix typo. Fixes #1221 PiperOrigin-RevId: 589835888 Change-Id: Iacedbe642709d5fbd43b7f0f1f9daa6447ce6155 --- doc/XMLreference.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/XMLreference.rst b/doc/XMLreference.rst index 2f423abf..6ca8c13b 100644 --- a/doc/XMLreference.rst +++ b/doc/XMLreference.rst @@ -172,7 +172,7 @@ This element does not strictly belong to MJCF. Instead it is a meta-element, use files in a single document object model (DOM) before parsing. The included file must be a valid XML file with a unique top-level element. This top-level element is removed by the parser, and the elements below it are inserted at the location of the :el:`include` element. At least one element must be inserted as a result of this procedure. The -:el:`include` element can be used where ever an XML element is expected in the MJFC file. Nested includes are allowed, +:el:`include` element can be used where ever an XML element is expected in the MJCF file. Nested includes are allowed, however a given XML file can be included at most once in the entire model. After all the included XML files have been assembled into a single DOM, it must correspond to a valid MJCF model. Other than that, it is up to the user to decide how to use includes and how to modularize large files if desired.