diff --git a/docs/concepts/deployments.mdx b/docs/concepts/deployments.mdx
index a7ae71b0..6af1bb79 100644
--- a/docs/concepts/deployments.mdx
+++ b/docs/concepts/deployments.mdx
@@ -1,10 +1,10 @@
 ---
-sidebar_position: 9
+sidebar_position: 10
 description: ""
 draft: "true"
 ---
 
-# Deployments & versions
+# Deployments & Versions
 
 Visualization of the service deployment hierarchy:
 
diff --git a/docs/concepts/durable_promises.mdx b/docs/concepts/durable_promises.mdx
new file mode 100644
index 00000000..f5378121
--- /dev/null
+++ b/docs/concepts/durable_promises.mdx
@@ -0,0 +1,7 @@
+---
+sidebar_position: 5
+description: ""
+draft: "true"
+---
+
+# Durable Promises
\ No newline at end of file
diff --git a/docs/concepts/durable_timers.mdx b/docs/concepts/durable_timers.mdx
index e72e0f10..22587905 100644
--- a/docs/concepts/durable_timers.mdx
+++ b/docs/concepts/durable_timers.mdx
@@ -1,11 +1,11 @@
 ---
-sidebar_position: 8
+sidebar_position: 6
 description: ""
 draft: "true"
 ---
 
 
-# Scheduling
+# Durable Timers & Scheduling
 
 - Durable sleep
 - Delayed calls
diff --git a/docs/concepts/event_processing.mdx b/docs/concepts/event_processing.mdx
deleted file mode 100644
index 2f075c6c..00000000
--- a/docs/concepts/event_processing.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-sidebar_position: 10
-description: ""
-draft: "true"
----
-
-# Event processing
-
-Why? Link to page on the website explaining the use case
-
-How it works
-- Restate subscription to Kafka topic. Via curl
-- Specify a function to execute per event
-
-Explain how Kafka partitioning maps to function invocations
\ No newline at end of file
diff --git a/docs/concepts/integrating_external_systems.mdx b/docs/concepts/integrating_external_systems.mdx
index 6b62bbef..e2faae43 100644
--- a/docs/concepts/integrating_external_systems.mdx
+++ b/docs/concepts/integrating_external_systems.mdx
@@ -1,11 +1,11 @@
 ---
-sidebar_position: 6
+sidebar_position: 8
 description: ""
 draft: "true"
 ---
 
 
-# Integrating systems
+# Push vs. pull model
 
 
 There are a few ways you can leverage Restate in external systems or facilitate communication between them and your Restate application.
diff --git a/docs/concepts/invocations.mdx b/docs/concepts/invocations.mdx
index 4807a9b2..bc5b6b9f 100644
--- a/docs/concepts/invocations.mdx
+++ b/docs/concepts/invocations.mdx
@@ -5,7 +5,7 @@ draft: "true"
 ---
 
 
-# Invocations
+# Durable RPC
 
 Two main type of invocations: inbound invocations and service-to-service invocations.
 
diff --git a/docs/concepts/lambda_suspendable_tasks.mdx b/docs/concepts/lambda_suspendable_tasks.mdx
index b10bf938..93cc447e 100644
--- a/docs/concepts/lambda_suspendable_tasks.mdx
+++ b/docs/concepts/lambda_suspendable_tasks.mdx
@@ -1,10 +1,10 @@
 ---
-sidebar_position: 5
+sidebar_position: 7
 description: ""
 draft: "true"
 ---
 
-# FaaS
+# Serverless Functions
 
 Restate works well with AWS Lambda because:
 link to website page on AWS Lambda workflows and blog post
diff --git a/docs/concepts/services_workflows_virtual_objects.mdx b/docs/concepts/services_workflows_virtual_objects.mdx
index c9abbe4d..30de3622 100644
--- a/docs/concepts/services_workflows_virtual_objects.mdx
+++ b/docs/concepts/services_workflows_virtual_objects.mdx
@@ -4,7 +4,7 @@ description: ""
 draft: "true"
 ---
 
-# Building blocks
+# Durable Functions, Workflows, Objects
 
 Restate gives you some building blocks to build your application with.
 
diff --git a/docs/concepts/state.mdx b/docs/concepts/state.mdx
index 38e31514..f4d6e254 100644
--- a/docs/concepts/state.mdx
+++ b/docs/concepts/state.mdx
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 7
+sidebar_position: 9
 description: ""
 draft: "true"
 ---