formatting updates, fix typos

a-mile · a-mile · commit 38084fd58c1a · 2025-07-23T15:45:03.000-04:00
diff --git a/LICENSE.md b/LICENSE.md
@@ -21,7 +21,7 @@ This tutorial has been adapted from the revised [RO-Crate introduction for 1.2](
 * Adaptation to Galaxy Training Material rendering
 * Explicit links to RO-Crate specifications
 * Example changed to different organization and license
-* Modiied for Carpentries style
+* Modified for Carpentries style
 
 # Examples
 
diff --git a/episodes/02-folder-as-crate-root.md b/episodes/02-folder-as-crate-root.md
@@ -56,7 +56,7 @@ We call the top-level folder of the crate for the **RO-Crate Root**
 and can now refer to its content with relative file paths.
 
 We also need to make some declaration within the JSON file to turn it into a valid _RO-Crate Metadata Document_,
-explained in the next session.
+explained in the next section.
 
 
 ## JSON-LD preamble
diff --git a/episodes/04-root-metadata.md b/episodes/04-root-metadata.md
@@ -68,6 +68,6 @@ It is still recommended to choose an overall Crate license that can legally appl
 ::::::::::::::::::::::::::::::::::::::::::::::::::
 
 :::::::::::::::::::::::::::::::::::::::: keypoints
-- Name, description, date published and license are required for the RO-Crate Root"
+- Name, description, date published and license are required for the RO-Crate Root
 - RO-Crate allows multiple licenses for different parts
 ::::::::::::::::::::::::::::::::::::::::::::::::::
diff --git a/episodes/07-data-entities.md b/episodes/07-data-entities.md
@@ -63,7 +63,7 @@ You can override the license for the root data entity by specifying a `license`
 
 For more information on describing files and folders,
 including their recommended and required attributes,
-see section on [data entities](https://www.researchobject.org/ro-crate/specification/1.2/data-entitites.html).
+see section on [data entities](https://www.researchobject.org/ro-crate/specification/1.2/data-entities.html).
 
 
 :::::::::::::::::::::::::::::::::::::::: keypoints
diff --git a/episodes/08-contextual-entities.md b/episodes/08-contextual-entities.md
@@ -58,9 +58,9 @@ Then define the instrument entity in the @graph.
 },    
 {
   "@id": "https://example.org/instrument/ws-2000",
-  "@type": "ThiIndividualProductng",
+  "@type": "IndividualProduct",
   "name": "WS-2000 Weather Station",
-  "description": "Automated weather station used to record temperature and rainfall data in Katoomba, Australia.",
+  "description": "Automated weather station used to record temperature and rainfall data.",
   "url": "https://example.org/instrument/ws-2000"
 },
 ```  
@@ -71,5 +71,5 @@ Then define the instrument entity in the @graph.
 :::::::::::::::::::::::::::::::::::::::: keypoints
 - Contextual entities are not considered part of the crate’s file structure
 - Instruments, software, and projects can be described as contextual entities
-- Cntextual entities can provide provenance about data capture and processing
+- Contextual entities can provide provenance about data capture and processing
 ::::::::::::::::::::::::::::::::::::::::::::::::::
diff --git a/episodes/09-authorship.md b/episodes/09-authorship.md
@@ -54,7 +54,7 @@ Moving back to the RO-Crate root `./`, let's specify who are the authors of the
 ## Who can be authors of an RO-Crate?
 
 When we say someone is an author of a crate,
-it means they have contributed something substansively to its content (typically the data).
+it means they have contributed something substantively to its content (typically the data).
 Agreement on what is considered authorship on a dataset can be tricky;
 you may decide some people would be better represented as `contributor`.
 One advantage of RO-Crate is that authorship can be declared explicitly also on each data entity,
diff --git a/episodes/10-validating.md b/episodes/10-validating.md
@@ -81,7 +81,7 @@ As an example, try the _Table_ button and notice that the entities with relative
 This is because when converting to RDF you need absolute URIs which do not readily exist when a crate is stored on disk,
 we've not decided where the crate is to be published yet.  
 
-::::::::::::::::::::::::::::::::::::::::keypoints
+:::::::::::::::::::::::::::::::::::::::: keypoints
 - RO-Crate metadata files are valid JSON-LD
 - The JSON-LD Playground can do basic validation and visualization
 - Further use of RO-Crate as Linked Data is possible, but may require handling of relative URI references
diff --git a/episodes/11-triples.md b/episodes/11-triples.md
@@ -19,7 +19,7 @@ e.g. to demonstrate how it might be described at a web resource,
 a 'base' URI is needed that will point to that resource,
 i.e. resolve as a page or file on the web.
 
-Try to specify a hypothetical base URI by modifing the graph's `@context` within the [JSON-LD Playground](https://json-ld.org/playground/)
+Try to specify a hypothetical base URI by modifying the graph's `@context` within the [JSON-LD Playground](https://json-ld.org/playground/)
 (do not modify the `ro-crate-metadata.json` on disk), and revisit the _Table_ rendering.
 
 ```json
diff --git a/episodes/12-html-preview.md b/episodes/12-html-preview.md
@@ -36,7 +36,7 @@ Try navigating the [preview of the running example](../files/rainfall-1.2.1/ro-c
 :::::::::::::::  solution
 1. CC BY-NC-SA 4.0 International
 2. Brown University
-3. The context, and for root dataset: existance, valid identifier, name, description, license and date published.  
+3. The context, and for root dataset: existence, valid identifier, name, description, license and date published.
 4. The other entities were not checked, e.g. the `affiliation` of the author.
 :::::::::::::::::::::::::
 ::::::::::::::::::::::::::::::::::::::::::::::::::
diff --git a/episodes/13-complete.md b/episodes/13-complete.md
@@ -56,9 +56,9 @@ The final RO-Crate Metadata Document constructed in this tutorial should look so
    },
    {
      "@id": "https://example.org/instrument/ws-2000",
-     "@type": "Thing",
+     "@type": "Individual Product",
      "name": "WS-2000 Weather Station",
-     "description": "Automated weather station used to record temperature and rainfall data in Katoomba, Australia.",
+     "description": "Automated weather station used to record temperature and rainfall data.",
      "url": "https://example.org/instrument/ws-2000"
    },    
    {
@@ -72,9 +72,7 @@ The final RO-Crate Metadata Document constructed in this tutorial should look so
      "@id": "https://orcid.org/0000-0002-1825-0097",
      "@type": "Person", 
      "name": "Josiah Carberry",
-     "affiliation": {
-       "@id": "https://ror.org/05gq02987"
-     }
+     "affiliation": { "@id": "https://ror.org/05gq02987" }
    },
    {
      "@id": "https://ror.org/05gq02987",
diff --git a/episodes/14-common-pitfalls.md b/episodes/14-common-pitfalls.md
@@ -52,7 +52,7 @@ Creating RO-Crate packages by hand is a great way to understand their structure,
 - **Problem**: Accidentally defining two entities with the same @id, or referencing an entity with an @id that doesn’t exist.
 - **Fix**: Ensure every @id is unique and points to an entity defined in the metadata.
 
-### 4. Forgetting required metadata on key entities
+### 5. Forgetting required metadata on key entities
 - **Problem**: The root dataset doesn’t have name or license, or files are missing type.
 - **Fix**: Always include the required fields for the root (./) and for files:
 ```json
diff --git a/episodes/15-next-steps.md b/episodes/15-next-steps.md
@@ -19,7 +19,7 @@ You have completed making a basic RO-Crate. You may try any of the following:
 
 - **More Contextual Entities**: Discover additional [contextual entities](https://www.researchobject.org/ro-crate/specification/1.2/contextual-entities.html) you can add to your crate, such as projects, grants, or related publications, to enrich the crate's context.
 
-- **Provenance and Software**: Learn how to describe the [provenance](https://www.researchobject.org/ro-crate/specification/1.2/provenance.html)(origin and history) of your data and include information about the [software](https://www.researchobject.org/ro-crate/specification/1.2/workflows.html) and workflows used in your research.
+- **Provenance and Software**: Learn how to describe the [provenance](https://www.researchobject.org/ro-crate/specification/1.2/provenance.html) (origin and history) of your data and include information about the [software](https://www.researchobject.org/ro-crate/specification/1.2/workflows.html) and workflows used in your research.
 
 - **RO-Crate Profiles**: Delve into [RO-Crate Profiles](https://www.researchobject.org/ro-crate/profiles.html), which are community-defined content checklists that extend the base specification to meet the specific needs of a domain or data type. Profiles impose conventions and may add domain specific terms/vocabularies, effectively making RO-Crates typed and machine-actionable for specific use cases. Examples include the [Workflow RO-Crate profile](https://about.workflowhub.eu/Workflow-RO-Crate/) used by WorkflowHub and the [Five Safes RO-Crate profile](https://trefx.uk/5s-crate/) for trusted workflow execution in Trusted Research Environments (TREs).
 
diff --git a/index.md b/index.md
@@ -9,8 +9,7 @@ packaging research data.
 
 :::::::::::::::::::::::::::::::::::::::::: prereq
 ## Prerequisites
-- Files and folder organization and using an editor/IDE
-- Files and folder organization and using a text editor or IDE such a [Visual Studio Code](https://code.visualstudio.com/)
+- Files and folder organization and using a text editor or IDE such as [Visual Studio Code](https://code.visualstudio.com/)
 ::::::::::::::::::::::::::::::::::::::::::::::::::
 
 ### Target Audience
