Various minor tune ups from code review

Co-authored-by: Kabilar Gunalan <[email protected]>

Author: yarikoptic

docs/59_overview.md

@@ -13,7 +13,7 @@ The DANDI platform is essentially composed of:
 2. **API**: A Django/Resonant-based backend application (hosted on Heroku) that handles the DANDI data model, user authentication, and orchestrates S3 interactions.
 3. **Frontend**: A Vue-based web application (hosted on Netlify) for users to browse, search, and manage data in the archive.
 4. **Workers**: Celery workers (also on Heroku) for asynchronous tasks such as file checksum calculations, analytics, and housekeeping.
-5. **Observability**: Log aggregation and alerting (Heroku logs, optional additional logs), plus Sentry for error-tracking and notifications. TODO(asmacdo) verify
+5. **Observability**: Log aggregation and alerting (Heroku logs, optional additional logs), plus Sentry for error-tracking and notifications.
 6. **Infrastructure-As-Code**: Terraform scripts that glue everything together—AWS S3 resources, Netlify or domain DNS, Heroku apps, etc.
 
 These services interconnect as follows:

docs/60_initialize_vendors.md

@@ -6,13 +6,13 @@ The DANDI ecosystem relies on vendor services to operate.  So first you will nee
 
 - **AWS**: Provides storage buckets, as well as domain management, for resources across the DANDI ecosystem. As well as the services (Kubernetes, etc.) for deploying the JupyterHub.
 
-- **GitHub**: Serves as the authentication provider for accounts across the DANDI ecosystem
+- **GitHub**: Serves as the authentication provider for accounts across the DANDI ecosystem.
 
 - **Terraform Cloud**: Manages provisioned resources across cloud vendors in a version-controlled manner. 
 
-- **Netlify**: Deploys production frontend build, as well as staging previews to assist with frontend development
+- **Netlify**: Deploys production frontend build, as well as staging previews to assist with frontend development.
 
-- **Sentry**: Provides observability and monitoring for API events
+- **Sentry**: Provides observability and monitoring for API events.
 
 Some services are not yet integrated within the main infrastructure:
 

docs/62_dandi_cli.md

@@ -5,7 +5,7 @@ The DANDI Client provides both a command line interface (CLI) and Python API.
 
 To reference your DANDI-clone API, [update the URLs reference per each CLI action](https://github.com/dandi/dandi-cli/blob/15196a93310618f8897c7b43444e216bbb094549/dandi/consts.py#L119-L135) and push a PR to the [dandi-cli GitHub repository](https://github.com/dandi/dandi-cli).
 
-Here is an example PR of another clone adding to the available instances of `DandiInstance` objects in `dandi-cli`: [see here](https://github.com/dandi/dandi-cli/pull/1527)
+Here is an [example PR](https://github.com/dandi/dandi-cli/pull/1527) of another clone adding to the available instances of `DandiInstance` objects in the `dandi-cli`.
 
 For example:
 
@@ -50,7 +50,7 @@ The DANDI Client leverages a tool called [versioneer](https://pypi.org/project/v
 Upon merging of a PR into `master`, if the `release` label is attached to the PR
 `versioneer` will generate a human-readable CHANGELOG entry, and then push to PyPI the new semantic version.  For more details on labeling `dandi-cli` pull requests, see [here](https://github.com/dandi/dandi-cli/blob/master/DEVELOPMENT.md#releasing-with-github-actions-auto-and-pull-requests).
 
-### Versioning-Realted Resources
+### Resources
 - [PyPI package](https://pypi.org/project/dandi/)
 - [Source code](https://github.com/dandi/dandi-cli)
 - [Developer instructions](https://github.com/dandi/dandi-cli/blob/master/DEVELOPMENT.md)