diff --git a/docs/60_initialize_vendors.md b/docs/60_initialize_vendors.md
index 5da02e55..370b5129 100644
--- a/docs/60_initialize_vendors.md
+++ b/docs/60_initialize_vendors.md
@@ -357,6 +357,10 @@ You can now invoke Terraform `plan` and `apply` from the Terraform Cloud UI or v
 
 The frontend for `dandi-archive` is served via [Netlify](https://www.netlify.com/)
 
+**Note:** A `Starter` plan should be plenty enough (specifically "build minutes" shouldn't exceed much past ~300 at most a month)
+-- if you'd like more control over specific deployments and environments, you
+may want to consider `Pro` -- [see here for more details](https://www.netlify.com/pricing/)
+
 ##### Create Account and Initialize Project
 
 First, create an account. After creating an account, you'll want to navigate to `Sites`, where you can `Add a new site`, and then `Import an existing project`
@@ -413,6 +417,8 @@ alt="retrieve"
 style="width: 60%; height: auto; display: block; margin-left: auto;  margin-right: auto;"/>
 <br/><br/>
 
+For your account, the free `Developer` account should be accurate, as define in [Sentry's pricing structure](https://sentry.io/pricing/)
+
 ##### Select Django as an App Type
 
 DANDI Archive API is built as a Django app -- so proceed to select `Django` on the following screen:
@@ -465,7 +471,7 @@ style="width: 60%; height: auto; display: block; margin-left: auto;  margin-righ
 <br/><br/>
 
 In terms of creating and publishing your first project, go to the [documentation for setting up a CLI and Python Client](.
-./47_cli_python)
+./62_dandi_cli)
 
 
 ## datalad (TBD)
diff --git a/docs/63_dandi_infrastructure.md b/docs/63_dandi_infrastructure.md
index 3315a1dc..6dc03ec3 100644
--- a/docs/63_dandi_infrastructure.md
+++ b/docs/63_dandi_infrastructure.md
@@ -121,6 +121,14 @@ style="width: 60%; height: auto; display: block; margin-left: auto;  margin-righ
 Lastly, validate your certificate via DNS Records. This can be done by using the CNAME values 
 expressed by the certificate and linking them as records in your DNS Hosted Zone.
 
+### Heroku Dyno Sizes
+
+`dandi-infrastructure` defines "dyno" (a.k.a process) sizes for each service being run. For specific reference,
+[see here in api.tf](https://github.com/dandi/dandi-infrastructure/blob/master/terraform/api.tf#L14-L18).
+
+While your DANDI Archive clone may differ in traffic and activity, the defaults set in `dandi-infrastructure` rarely
+exceed 75% usage.
+
 ### Heroku API Domain
 
 Heroku will provision an API endpoint for your DANDI Archive. In order to properly map and configure that domain, first proceed to the 
diff --git a/docs/64_dandi_archive.md b/docs/64_dandi_archive.md
index 28f85d30..57e86eb7 100644
--- a/docs/64_dandi_archive.md
+++ b/docs/64_dandi_archive.md
@@ -26,6 +26,8 @@ you'll see several entries:
 
 This `Procfile` shouldn't need to be changed or reconfigured much for a DANDI-clone; however, it is important to note so that one may understand how DANDI Archive is working.
 
+For information on the resource allocation of `dynos` in DANDI Archive, please reference documentation in [the Dandi Infrastructure Docs](../63_dandi_infrastructure)
+
 ## Understanding metrics and logging via Heroku
 
 Heroku provides observability in a very convenient manner. If you'd like to see what is happening with your app in real-time, simply access the options shown in the image below