Feedback

Author: bamurtaugh

_posts/2023-08-22-prebuild.md

@@ -1,12 +1,8 @@
 ---
 layout: post
 title:  "Speed Up Your Workflow with Prebuilds"
-authors:
-  - "@bamurtaugh"
-  - "@craiglpeters"
-authorUrls:
-  - "https://github.com/bamurtaugh"
-  - "https://github.com/craiglpeters"
+author: "@bamurtaugh"
+authorUrl: https://github.com/bamurtaugh
 ---
 
 Getting dev containers up and running for your projects is exciting - you've unlocked environments that include all the dependencies your projects need to run, and you can spend so much more time on coding rather than configuration. 
@@ -23,7 +19,7 @@ We should first define: What is prebuilding?
 
 If you're already using dev containers, you're likely already familiar with the idea of building a container, where you package everything your app needs to run into a single unit. 
 
-You need to build your container once it has all the dependencies it needs, and rebuild anytime you add new dependencies. Since you may not need to rebuild often, it might be alright if it takes a while for that initial build. But if you or your teammates need to use that container on another machine, you'll need to wait for it to build it again in those new environments.
+You need to build your container once it has all the dependencies it needs, and rebuild anytime you add new dependencies. Since you may not need to rebuild often, it might be alright if it takes a while for that initial build. But if you or your teammates need to use that container on another machine, you'll need to wait for it to build again in those new environments.
 
 > **Note:** The [dev container CLI doc](/_implementors/reference.md#prebuilding) is another great resource on prebuilding.
 
@@ -87,6 +83,8 @@ Let's walk through the Kubernetes prebuild as an example of how you can determin
      * We can explore what each of them installs in their associated repo. Most appear to be defined in the [devcontainers/features repo](https://github.com/devcontainers/features/tree/main/src) as part of the dev container spec
 * **Modify and rebuild as desired**
      * If I'd like to add more content to my dev container, I can either modify my end user dev container (i.e. the one in the main Kubernetes repo), or modify the config defining the prebuilt image (i.e. the content in Craig's dev container)
+          * For more universal changes that anyone using the prebuilt image should get, update the config defining the prebuilt image
+          * For more project or user specific changes (i.e. a language I need in my project but other folks using this container won't necessarily need in theirs, or settings I prefer for my editor environment), update the end user dev container
      * Features are a great way to add dependencies in a clear, easily packaged way
 
 ## <a href="#benefits" name="benefits" class="anchor"> Benefits </a>