docs: remove backward-looking workflow references

Author: cedaraspen

docs/capabilities/devvit-web/devvit_web_overview.mdx

@@ -94,6 +94,6 @@ Use `/internal/` for Devvit-managed handlers declared in `devvit.json`, such as
 
 ### Configuration in `devvit.json`
 
-`devvit.json` is the configuration file for Devvit apps. It defines an app's post configuration, Node.js server configuration, permissions, scheduled jobs, event triggers, menu entries, payments configuration, and project settings. `devvit.json` replaces the legacy `devvit.yaml` configuration. A project should have one or the other but not both.
+`devvit.json` is the configuration file for Devvit apps. It defines an app's post configuration, Node.js server configuration, permissions, scheduled jobs, event triggers, menu entries, payments configuration, and project settings.
 
 Learn more about [devvit.json](./devvit_web_configuration.md)

docs/examples/tutorials/mod-tool.md

@@ -4,8 +4,6 @@ slug: /examples/tutorials/mod-tool
 
 # Build a Mod Tool
 
-The older Three Strikes tutorial has been replaced by the current Devvit Web mod-tool path.
-
 If you're building a new moderator workflow today, start with:
 
 - [Quickstart for Mod Tools](../../quickstart/quickstart-mod-tool.md)

docs/guides/faq.mdx

@@ -185,11 +185,11 @@ For current Devvit Web apps, customize the first screen through your `post.entry
 
 </details>
 
-<span id="should-i-use-the-legacy-splash-field-or-html-launch-entry-points"></span>
+<span id="should-i-use-splash-or-html-launch-entry-points"></span>
 <details>
-<summary>Should I use the legacy <code>splash</code> field or HTML launch entry points?</summary>
+<summary>Should I use <code>splash</code> or HTML launch entry points?</summary>
 
-Prefer HTML launch entry points for new work. The older `splash` parameter is still documented, but the migration guide marks it as deprecated in favor of entrypoint-based launch screens and `entry` selection in `submitCustomPost()`. If you are updating an older app or wondering why splash changes are confusing, start with [Migrating from Splash Screens](../capabilities/server/launch_screen_and_entry_points/splash_migration.mdx).
+Use HTML launch entry points. Configure launch screens through your `post.entrypoints` in `devvit.json` and `entry` selection in `submitCustomPost()`. The main references are [Launch overview](../capabilities/server/launch_screen_and_entry_points/launch_overview.mdx), [View modes and entry points](../capabilities/server/launch_screen_and_entry_points/view_modes_entry_points.md), and [Launch screen customization](../capabilities/server/launch_screen_and_entry_points/launch_screen_customization.md).
 
 </details>