Skip to content

Commit

Permalink
remove end of line spaces
Browse files Browse the repository at this point in the history
  • Loading branch information
stevebachmeier committed Aug 27, 2024
1 parent 856d28d commit 7fd0380
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions docs/source/concepts/entry_points.rst
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ model_specification
As an argument ot the
:class:`SimulationContext <vivarium.framework.engine.SimulationContext>`, it
can be provided as a path to a file (either as a :class:`str` or a
:class:`pathlib.Path`) or as a
:class:`pathlib.Path`) or as a
:class:`LayeredConfigTree <layered_config_tree.main.LayeredConfigTree>`, the internal
representation of configuration information used by :mod:`vivarium`. The
model specification contains three pieces, each represented by the next
Expand All @@ -51,8 +51,8 @@ components
of a :mod:`vivarium` simulation. They are python classes that interact with
the framework via the :ref:`builder <builder_concept>`. Components may be
provided to the context as a list of instantiated objects, as a dictionary
representation of their import paths, or as a
:class:`LayeredConfigTree <layered_config_tree.main.LayeredConfigTree>`
representation of their import paths, or as a
:class:`LayeredConfigTree <layered_config_tree.main.LayeredConfigTree>`
representation of their import paths. The latter two representations are
treated as prefix trees when they are parsed into objects. This behavior
is controlled by the
Expand All @@ -62,15 +62,15 @@ components
configuration
The :term:`configuration <Configuration>` is the set of
variable model parameters in a :mod:`vivarium` simulation. It may be
provided as a dictionary or
provided as a dictionary or
:class:`LayeredConfigTree <layered_config_tree.main.LayeredConfigTree>` representation. See
the :ref:`concept note <configuration_concept>` for more information.
plugins
:term:`Plugins <Plugin>` represent core functionality and
subsystems of a :mod:`vivarium` simulation. Users may wish to extend the
functionality of the framework by writing their own plugins. The framework
then needs to be notified of their names and where they are located. Plugins
may be specified as either a dictionary or
may be specified as either a dictionary or
:class:`LayeredConfigTree <layered_config_tree.main.LayeredConfigTree>` and are
parsed into objects by the
:class:`PluginManager <vivarium.framework.plugins.PluginManager>`.
Expand All @@ -82,7 +82,7 @@ modification of a simulation defined in a model specification file.

.. warning::

If you provide ``components`` as a :class:`dict` or
If you provide ``components`` as a :class:`dict` or
:class:`LayeredConfigTree <layered_config_tree.main.LayeredConfigTree>`,
these will also be treated as overrides, though this is almost never the
intended use case, so tread cautiously.
Expand Down

0 comments on commit 7fd0380

Please # to comment.