Skip to content

Commit 1ebe5d5

Browse files
drewoldagCopilot
andauthored
Fixing typos on the core concepts page (#598)
* Scaffolding page for core concepts page. * Added required-inputs page. * Responding to PR feedback. Adding required_input diagram. * Resolving more PR comments. * Update docs/required_input.rst Co-authored-by: Copilot <[email protected]> --------- Co-authored-by: Copilot <[email protected]>
1 parent dbe23cc commit 1ebe5d5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/required_input.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,14 +36,14 @@ an example of specifying a built-in dataset for training.
3636

3737
Prepare the data
3838
----------------
39-
To support reusablility, Hyrax encourages the separation of datasets and models.
39+
To support reusability, Hyrax encourages the separation of datasets and models.
4040
i.e. the form of the data provided by a dataset class should not be customized for a
4141
specific model, nor should a model architecture be hardcoded to a specific dataset.
4242

4343
In order to convert the content of a dataset into a form that is suitable for a model,
4444
Hyrax requires a user-defined function that will prepare the data for the model.
4545

46-
As a contrived example, consider a dataset where each data point is a composed of
46+
As a contrived example, consider a dataset where each data point is composed of
4747
three 2d arrays: "science", "mask", and "variance".
4848
To be flexible, the dataset class that provides data from disk would return each
4949
array individually.

0 commit comments

Comments
 (0)