Deep Dive updates:

happy-path/index.html.markerb

@@ -29,9 +29,10 @@ A real-world application has, at a minimum, the following components:
 
 To get a fully-functional app running smoothly, you need a whole bunch of things; things like Anycast routing, load balancers, DNS certificates, WebSockets, an internal private network, a relational database, an object store, and an in-memory database. And the knowledge to connect them all together.
 
-We take a lot of this work off your plate with our [Fly Proxy routing](/docs/reference/fly-proxy/) and out-of-the-box [private networking](/docs/networking/private-networking/).
+Connecting complex compoents together generally takes an unpredictable amount of time due to surprises.  Usually, set up for a complete app typically takes a _minimum_ of an afternoon's worth of work, even if you're familiar with a cloud platform.  We will be up and running in minutes.
 
-Usually, set up for a complete app typically takes a _minimum_ of an afternoon's worth of work, even if you're familiar with a cloud platform. There is almost always a surprise, and often several. We can't promise no surprises, but we can show you how we'll partner with you to handle some of the dev ops complexities of working in a public cloud.
+Fly.io minimizes surprises by taking a lot of work off your plate with our [Public Network Services](https://fly.io/docs/networking/services/), [Fly Proxy routing](/docs/reference/fly-proxy/), out-of-the-box [Private Networking](/docs/networking/private-networking/), and preconfigured databases.
+While we can't promise no surprises, we can show you how we'll partner with you to handle some of the dev ops complexities of working in a public cloud.
 
 ## So what is this deep dive demo app?
 
@@ -50,16 +51,13 @@ The demo includes the following components:
 * A [Tigris bucket](https://www.tigrisdata.com/+external) to store the audio files
 * [Upstash for Redis](https://fly.io/docs/reference/redis/) and [WebSockets](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API+external) to handle the connections for the realtime requirement
 
-## Available runtimes
+### Available runtimes
 
-Our deep dive demo comes in two flavors (so far):
+Our deep dive demo comes in three flavors (so far):
 
-- **Node.js** 
-  - [node-dictaphone](https://github.com/fly-apps/node-dictaphone+external) GitHub repo
-  - For details about implementation-specific files and app logic, see [Node.js deep dive demo](/docs/happy-path/nodejs/).
-- **Rails**
-  - [rails-dictaphone](https://github.com/fly-apps/rails-dictaphone+external) GitHub repo
-  - For details about implementation-specific files and app logic, see [Rails deep dive demo](/docs/happy-path/rails/).
+  * [Node.js](/docs/happy-path/nodejs/)
+  * [Rails](/docs/happy-path/rails/)
+  * [Django](/docs/happy-path/django/)
 
 ---
 

happy-path/launch-deep-dive.html.markerb

@@ -7,7 +7,7 @@ order: 3
 
 This is the point where you might expect to see that the marketing hype promised by [Speedrun](https://fly.io/speedrun) doesn't quite cut it. But the fact is that Fly.io is built for an excellent developer experience (DX) for full stack applications with both realtime time and object storage requirements.
 
-**Step 0:** To get set up to run the deep dive demo on Fly.io, all you need to do is install Ruby or Node and create an empty project directory. 
+**Step 0:** To get set up to run the deep dive demo on Fly.io, all you need to do is install Ruby, Node, or Python and create an empty project directory. 
 
 After that there are only two steps.
 
@@ -45,6 +45,8 @@ Optional, but details are provided for each runtime:
 
   * [Node.js](../nodejs/)
   * [Rails](../rails/)
+  * [Django](../django/)
+
 
 ---