From 7998fc7fcaca59834156cbbc4706922232f525cf Mon Sep 17 00:00:00 2001 From: Yuval Tassa Date: Fri, 5 May 2023 08:11:24 -0700 Subject: [PATCH] Fix typo. PiperOrigin-RevId: 529719905 Change-Id: I7ad8b333465db5f453b0d6b2ade02fbfc39a96a9 --- doc/programming/extension.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/programming/extension.rst b/doc/programming/extension.rst index 22b3ce4a..a20d579a 100644 --- a/doc/programming/extension.rst +++ b/doc/programming/extension.rst @@ -254,7 +254,7 @@ Resource providers Resource providers extend MuJoCo to load assets (XML files, meshes, textures, and etc.) that don't necessarily come from the OS filesystem or the Virtual File System (:ref:`mjVFS`). For example, downloading assets from the Internet could be -implemented as a resource provider. These extensions are handle abstractly in MuJoCo via the :ref:`mjResource` struct. +implemented as a resource provider. These extensions are handled abstractly in MuJoCo via the :ref:`mjResource` struct. .. _exProviderStructure: @@ -281,7 +281,7 @@ Resource prefix Callbacks There are three callbacks that a resource provider is required to implement: :ref:`open`, :ref:`read`, and :ref:`close`. A fourth callback :ref:`getdir` - which is optional. More details on these callbacks are given below. + is optional. More details on these callbacks are given below. Data Pointer Lastly, there's an opaque data pointer for the provider to pass data into the callbacks. This data pointer is constant