diff --git a/README.md b/README.md
index 9bf7a28..ed452c6 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,7 @@
 [![Crates.io](https://img.shields.io/crates/v/duroxide.svg)](https://crates.io/crates/duroxide)
 [![Documentation](https://docs.rs/duroxide/badge.svg)](https://docs.rs/duroxide)
 
-> Notice: This is an alpha version
+> **Preview:** This project is currently in preview.
 
 A lightweight and embeddable durable execution runtime for Rust. Inspired by the [Durable Task Framework](https://github.com/Azure/durabletask) and [Temporal](https://temporal.io/).
 
diff --git a/docs/proposals-impl/unregistered-orchestration-backoff.md b/docs/proposals-impl/unregistered-orchestration-backoff.md
index 27a115f..4665cdb 100644
--- a/docs/proposals-impl/unregistered-orchestration-backoff.md
+++ b/docs/proposals-impl/unregistered-orchestration-backoff.md
@@ -96,7 +96,7 @@ Benefits:
 - No new configuration options
 - Consistent behavior with other "repeatedly failing" scenarios
 - Single code path for "message keeps bouncing"
-- Already tested and production-ready
+- Already tested and ready to reuse
 
 ### Exponential Backoff Calculation
 
diff --git a/docs/proposals/replay-engine-versioning-test.md b/docs/proposals/replay-engine-versioning-test.md
index 437925a..0560cc5 100644
--- a/docs/proposals/replay-engine-versioning-test.md
+++ b/docs/proposals/replay-engine-versioning-test.md
@@ -259,4 +259,4 @@ With `replay-version-test` disabled:
 - No new test code compiled
 - Binary output identical to pre-change
 
-This feature exists purely to verify the versioning mechanism works. It is not a production feature.
+This feature exists purely to verify the versioning mechanism works. It is preview validation scaffolding.
diff --git a/docs/versioning-best-practices.md b/docs/versioning-best-practices.md
index 8cfead0..13e8fa3 100644
--- a/docs/versioning-best-practices.md
+++ b/docs/versioning-best-practices.md
@@ -156,7 +156,7 @@ T+1:02  UI/API refreshes → now shows v1.0.2
    /// - Added retry logic for health checks
    ```
 
-5. **Test version transitions** in development before production
+5. **Test version transitions** in development before rollout
    - Deploy new version
    - Verify old version completes its cycle
    - Verify new version starts after `continue_as_new`
diff --git a/examples/README.md b/examples/README.md
index aa0e66d..a588688 100644
--- a/examples/README.md
+++ b/examples/README.md
@@ -176,7 +176,7 @@ After running these examples:
 1. **Read the documentation**: Check `docs/ORCHESTRATION-GUIDE.md` for the complete guide
 2. **Explore the test suite**: Look at `tests/e2e_samples.rs` for more complex scenarios
 3. **Build your own**: Start with a simple orchestration and gradually add complexity
-4. **Join the community**: This is an experimental project - contributions welcome!
+4. **Join the community**: Duroxide is currently in preview - contributions welcome!
 
 ## Troubleshooting
 
diff --git a/src/provider_stress_tests.rs b/src/provider_stress_tests.rs
index 25d9c14..5983b48 100644
--- a/src/provider_stress_tests.rs
+++ b/src/provider_stress_tests.rs
@@ -127,7 +127,7 @@
 //!
 //! ## Interpreting Results
 //!
-//! **Success Rate**: Should be 100% for production-ready providers. Any failures indicate issues:
+//! **Success Rate**: Should be 100% for providers under stress validation. Any failures indicate issues:
 //! - Infrastructure failures: Provider bugs, lock issues, data corruption
 //! - Configuration failures: Missing implementations, nondeterminism detection
 //! - Application failures: Expected orchestration/activity errors (should be rare in stress tests)