diff --git a/docs/docs/get-started/basic-concepts.md b/docs/docs/get-started/basic-concepts.md
index 5fe94293e1..1c3f4a604e 100644
--- a/docs/docs/get-started/basic-concepts.md
+++ b/docs/docs/get-started/basic-concepts.md
@@ -10,13 +10,13 @@ Package
A package defines the set up logic for a containerized backend. Packages can be accessed via Github locators.
-```bash
+```console
kurtosis run github.com/kurtosis-tech/basic-service-package
```
Packages can accept a set of parameters, defined by the package author, which enable the package consumer to modify their deployed backend at a high-level without needing to know how to configure each individual service.
-```bash
+```console
kurtosis run github.com/kurtosis-tech/basic-service-package \
'{"service_a_count": 2,
"service_b_count": 2,
@@ -27,31 +27,19 @@ kurtosis run github.com/kurtosis-tech/basic-service-package \
Enclave
-----------
-An enclave is a "walled garden" in which Kurtosis runs a containerized backend. Enclaves can run anywhere that you have a Docker engine or a Kubernetes cluster. The main purposes of an enclave are resource isolation and "garbage collection". With an "enclave remove" command (`kurtosis enclave rm`), you can destroy all of the resources used to set up your environment and leave nothing hanging around on your machine(s).
+An enclave is a "walled garden" in which Kurtosis runs a containerized backend. Enclaves can run anywhere that you have a Docker engine or a Kubernetes cluster. The main purposes of an enclave are resource isolation and "garbage collection".
-Plan
------------
-
-The "plan" is the series of instructions, encoded in a package, that runs in an enclave. Each instruction in a plan is a basic building block for spinning up a containerized backend. You can see the plan that a package will run by "dry-running" the package:
-
-```bash
-kurtosis run --dry-run github.com/kurtosis-tech/basic-service-package
-```
-
-Rendered Plan
+With an "enclave remove" command (`kurtosis enclave rm`), you can destroy all of the resources used to set up your environment and leave nothing hanging around on your machine(s).
-```title="Steps in the Plan"
-> render_templates
-
-> add_services configs={"service-a-1": ServiceConfig(image="h4ck3rk3y/service-a", ports={"frontend": PortSpec(number=8501, application_protocol="http")}, files={"/app/config": "slender-boulder"})}
-
-> render_templates
+Files Artifact
+-----------
-> add_services configs={"service-b-1": ServiceConfig(image="h4ck3rk3y/service-b", ports={"frontend": PortSpec(number=8501, application_protocol="http")}, files={"/app/config": "purple-comet"}, cmd=["false"])}
+A files artifact is a set of files shipped with, or generated by, a package. Files artifacts are typically used for rendering configuration files that must be dynamically generated when an environment spins up, or for shipping static configuration files that must be shared across multiple services.
-> render_templates
+When you run a package, you can see the files artifacts that the package uses in the enclave output:
-> add_services configs={"service-c-1": ServiceConfig(image="h4ck3rk3y/service-c", ports={"frontend": PortSpec(number=8501, application_protocol="http")}, files={"/app/config": "arctic-oak"}, env_vars={"PARTY_MODE": "false"})}
+```console
+kurtosis run github.com/kurtosis-tech/basic-service-package
```
-TL;DR Version
+You should get output that looks like:
-This quickstart is in a "code along" format. You can also dive straight into running the end results and exploring the code too.
-
-**Open the Playground: [Start](https://gitpod.io/?autoStart=true&editor=code#https://github.com/kurtosis-tech/ethereum-package)**
+
-Click on the "New Workspace" button! You don't have to worry about the Context URL, Editor or Class. It's all pre-configured for you.
-
-More ways to interact with an enclave
+
+You can also do a set of actions you would expect from a standard Docker or Kubernetes deployments, like:
+1. Shell into a service: `kurtosis service shell quickstart service-c-1`
+2. See a service's logs: `kurtosis service logs quickstart service-c-1`
+3. Execute a command on a service: `kurtosis service exec quickstart service-c-1 'echo hello world'`
+
+See that the count of each service changed
+
+You can see 2 instances of Service A and 2 instances of Service B in the CLI output:
+
+
+
+You can verify that the configuration file of Service C has been properly changed so it can talk to all 4 of them:
+
+```console
+kurtosis files download quickstart service-c-rendered-config
+```
```console
-kurtosis run github.com/kurtosis-tech/ethereum-package --args-file ~/network_params.yaml --enclave eth-network
+cat service-c-rendered-config/service-config.json
+```
+You should see the rendered config file with the contents:
+```
+{
+ "service-a": [{"name": "service-a-1", "uri": "172.16.16.4:8501"},{"name": "service-a-2", "uri": "172.16.16.7:8501"}],
+ "service-b": [{"name": "service-b-1", "uri": "172.16.16.5:8501"},{"name": "service-b-2", "uri": "172.16.16.8:8501"}]
+}
```
-Kurtosis will then begin to spin up your private Ethereum testnet by interpreting the instructions in the Kurtosis package, validating the plan to ensure there are no conflicts or obvious errors, and then finally executes the plan (read more about multi-phase runs [here][multi-phase-runs-reference]). Kurtosis first spins up an isolated, ephemeral environment on your machine called an [enclave][enclaves-reference] where all the services and [files artifacts][files-artifacts-reference] for your system will reside in. Then, those services will be bootstrapped and required files generated to start up the system.
+See a feature flag turned on by a configuration file on disk
+Service A has the `party_mode` flagged turned on by virtue of its configuration file. You can see that with by downloading the `service-a-rendered-config` files artifact, as you've seen before:
+
+```console
+kurtosis files download quickstart service-a-rendered-config
+```
```console
-INFO[2023-08-28T13:05:31-04:00] ====================================================
-INFO[2023-08-28T13:05:31-04:00] || Created enclave: eth-network ||
-INFO[2023-08-28T13:05:31-04:00] ====================================================
-Name: eth-network
-UUID: e1a41707ee8e
-Status: RUNNING
-Creation Time: Mon, 28 Aug 2023 13:04:53 EDT
-
-========================================= Files Artifacts =========================================
-UUID Name
-a662c7c74685 1-lighthouse-geth-0-63
-6421d80946ce 2-lighthouse-geth-64-127
-a1ad3962f148 cl-genesis-data
-730d585d5ec5 el-genesis-data
-c1e452ad7e53 genesis-generation-config-cl
-284cde692102 genesis-generation-config-el
-b03a5b7b9340 geth-prefunded-keys
-013f5d8708fa prysm-password
-
-========================================== User Services ==========================================
-UUID Name Ports Status
-202516f0ff8f cl-1-lighthouse-geth http: 4000/tcp -> http://127.0.0.1:65191 RUNNING
- metrics: 5054/tcp -> http://127.0.0.1:65192
- tcp-discovery: 9000/tcp -> 127.0.0.1:65193
- udp-discovery: 9000/udp -> 127.0.0.1:64174
-66bdfbd6c066 cl-1-lighthouse-geth-validator http: 5042/tcp -> 127.0.0.1:65236 RUNNING
- metrics: 5064/tcp -> http://127.0.0.1:65237
-b636913d4d03 cl-2-lighthouse-geth http: 4000/tcp -> http://127.0.0.1:65311 RUNNING
- metrics: 5054/tcp -> http://127.0.0.1:65312
- tcp-discovery: 9000/tcp -> 127.0.0.1:65310
- udp-discovery: 9000/udp -> 127.0.0.1:51807
-e296eefa1710 cl-2-lighthouse-geth-validator http: 5042/tcp -> 127.0.0.1:65427 RUNNING
- metrics: 5064/tcp -> http://127.0.0.1:65428
-4df1beb0203d el-1-geth-lighthouse engine-rpc: 8551/tcp -> 127.0.0.1:65081 RUNNING
- rpc: 8545/tcp -> 127.0.0.1:65079
- tcp-discovery: 30303/tcp -> 127.0.0.1:65078
- udp-discovery: 30303/udp -> 127.0.0.1:55146
- ws: 8546/tcp -> 127.0.0.1:65080
-581a0fe5de77 el-2-geth-lighthouse engine-rpc: 8551/tcp -> 127.0.0.1:65130 RUNNING
- rpc: 8545/tcp -> 127.0.0.1:65132
- tcp-discovery: 30303/tcp -> 127.0.0.1:65131
- udp-discovery: 30303/udp -> 127.0.0.1:49475
- ws: 8546/tcp -> 127.0.0.1:65129
-4980884d9bb0 prelaunch-data-generator-cl-genesis-data RUNNING
-3174baf6a6ff prelaunch-data-generator-el-genesis-data RUNNING
+cat service-a-rendered-config/service-config.json
+```
+You should see the config file contents with the feature flag turned on:
+```
+{
+ "party_mode": true
+}
```
-Thats it! You now have a full, private Ethereum blockchain on your local machine.
+See a feature flag turned on by an command line argument
-Next, you'll see a section dedicated to [Files Artifacts](https://docs.kurtosis.com/advanced-concepts/files-artifacts/), which are Kurtosis' first-class representation of data inside your enclave, stored as compressed TGZ files. You'll notice there are configuration files for the nodes, grafana, and prometheus as well as private keys for pre-funded accounts and genesis-related data. These files artifacts were generated and used by Kurtosis to start the network and abstracts away the complexities and overhead that come with generating validator keys and getting genesis and node config files produced and mounted to the right containers yourself.
+Service B has the `party_mode` flag turned on by virtue of a command line flag. To see this, run:
+```console
+kurtosis service inspect quickstart service-b-1
+```
-Lastly, there is a section called `User Services` which display the number of services (running in Docker containers) that make up your network. You will notice that there are 2 Ethereum nodes comprised of 3 services each (an EL client, a CL beacon client, and a CL validator client) and 2 genesis data generators for each the CL and EL. Each of these services are running in Docker containers inside your local enclave & Kurtosis has automatically mapped each container port to your machine's ephemeral ports for seamless interaction with the services running in your enclave.
+You should see, in the output, the CMD block indicating that the flag was passed as a command line argument to the server process:
+```console
+CMD:
+ --
+ --party-mode
+```
-Why Kurtosis packages - from a consumer's perspective
------------------------------------------------------
-Kurtosis was built to make building distributed systems as easy as building a single server app. Kurtosis aims to achieve this by bridging the environment definition author-consumer divide. Tactically, this means making it dead simple for a consumer (like yourself) to pick up an environment definition, spin it up, and deploy it the way you want, where you want - all without needing to know specialized knowledge about how the system works or how to use Kubernetes or Docker.
+See a feature flag turned on by an environment variable
-There are many other reasons why we believe Kurtosis is the right tool for bridging the author-consumer divide. Check out the [next guide][how-to-set-up-postgres-guide] to experience the workflow for a package author and how Kurtosis improves the developer experience for an environment definition author.
+Service C has the `party_mode` flag turned on by virtue of an environment variable. To see the environment variable flag is indeed enabled, run:
-Conclusion
-----------
-And that's it - you've successfully used Kurtosis to instantiate a full, private Ethereum testnet - one of the most complex distributed systems in todays time.
+```console
+kurtosis service inspect quickstart service-c-1
+```
-Let's review. In this tutorial you have:
+In the output, you will see a block called `ENV:`. In that block, you should see the environment variable `PARTY_MODE: true`.
-1. Installed Kurtosis and Docker.
-2. Configure how your system should look like, using parameters that are passed in at runtime.
-3. Run a single command to spin up your network.
-4. Reviewed how package consumers benefit from using environment definitions written for Kurtosis.
+