Apply suggestions from code review

Co-authored-by: Copilot <[email protected]>

Author: satra

docs/terms-policies/governance.md

@@ -52,7 +52,7 @@ The DANDI Project codebase includes the components listed in the table below:
 | Archive | [dandi-archive](https://github.com/dandi/dandi-archive), [dandi-infrastructure](https://github.com/dandi/dandi-infrastructure) |
 | Client | [dandi-cli](https://github.com/dandi/dandi-cli), [dandidav](https://github.com/dandi/dandidav) |
 | Metadata | [dandi-schema](https://github.com/dandi/dandi-schema), [schema](https://github.com/dandi/schema) |
-| JupterHub | [dandi-hub](https://github.com/dandi/dandi-hub), [nebari](https://github.com/dandi/nebari), [nebari-deployments](https://github.com/dandi/nebari-deployments), [nebari-docker-images](https://github.com/dandi/nebari-docker-images) |
+| JupyterHub | [dandi-hub](https://github.com/dandi/dandi-hub), [nebari](https://github.com/dandi/nebari), [nebari-deployments](https://github.com/dandi/nebari-deployments), [nebari-docker-images](https://github.com/dandi/nebari-docker-images) |
 | Documentation & Support | [dandi-docs](https://github.com/dandi/dandi-docs), [dandi-about](https://github.com/dandi/dandi-about), [helpdesk](https://github.com/dandi/helpdesk) |
 
 Multiple deployments of this codebase operate as separate instances, each serving distinct research communities and datasets. The DANDI Archive instance is available at https://dandiarchive.org/, and the EMBER-DANDI Archive instance is available at https://dandi.emberarchive.org/. This document governs over the DANDI Project codebase unless otherwise specified.
@@ -149,7 +149,7 @@ Administrators:
 1. Open a GitHub issue describing the bug/feature request, context, and possible solutions.
 2. For major architectural changes, create a design document and submit as a PR for discussion and refinement.
    For reference, see [previous design documents](https://github.com/dandi/dandi-archive/tree/master/doc).
-3. Collect feedback during a 7 day review period.
+3. Collect feedback during a 7-day review period.
 4. Summarize consensus in the GitHub issue and resolve all suggestions in the design document.
 5. Implement via pull request(s) referencing the proposed design.
 
@@ -175,7 +175,7 @@ Administrators:
     - All comments must be resolved or addressed.
     - If a comment cannot be resolved, the Project Leadership would be enlisted to decide on the path forward.
     - Approval by at least 1 listed Maintainer for that repository.
-    - 24 hour waiting period (unless addressing a critical issue or trivial issue [e.g. typos]).
+    - 24-hour waiting period (unless addressing a critical issue or trivial issue [e.g. typos]).
 - See section below regarding updates to the Governance document.
 
 ### 7.3 Draft vs Ready for Review