Remove a doc

Author: theletterf

get-started/toc.yml

@@ -6,7 +6,6 @@ toc:
       - file: trial-choose-use-case.md
       - file: trial-week-1.md
       - file: trial-week-2.md
-      - file: trial-poc-framework.md
   - file: introduction.md
     children:
       - file: the-stack.md

get-started/trial-choose-use-case.md

@@ -28,7 +28,7 @@ Answer these questions to identify your primary use case:
 
 ## Solution overview
 
-### Elasticsearch (Search)
+### Elasticsearch (search)
 
 **Best for**: Building search experiences, analyzing business data, and gaining insights from large datasets.
 
@@ -46,11 +46,11 @@ Answer these questions to identify your primary use case:
 - You're building an application that requires fast, relevant search.
 - You want to create custom analytics dashboards for business data.
 
-**What you'll build in your trial**:
+**What you will build in your trial**:
 - A searchable index of your data (documents, products, or events).
 - Custom search queries with filters and relevance tuning.
 - Basic analytics and visualizations.
-- A simple search interface or dashboard.
+- An efficient search interface or dashboard.
 
 **Time to value**: See search results within 1-2 hours of ingesting data.
 
@@ -69,11 +69,11 @@ Answer these questions to identify your primary use case:
 **Your organization might need this if**:
 - Applications are slow or experiencing errors.
 - You have limited visibility into system performance.
-- Logs are scattered across multiple systems.
-- You need to meet SLAs or track system uptime.
+- Logs exist across multiple systems.
+- You need to meet service-level agreements (SLAs) or track system uptime.
 - Troubleshooting incidents takes too long.
 
-**What you'll build in your trial**:
+**What you will build in your trial**:
 - Monitoring for 2-3 key services or hosts.
 - Log aggregation from critical applications.
 - Performance dashboards and health metrics.
@@ -101,7 +101,7 @@ Answer these questions to identify your primary use case:
 - Compliance requires security event tracking.
 - Incident response is manual and time-consuming.
 
-**What you'll build in your trial**:
+**What you will build in your trial**:
 - Security data ingestion from key systems (endpoints, network, cloud).
 - Detection rules for common threats.
 - Security dashboards and timelines.
@@ -133,15 +133,13 @@ After you've selected your use case:
 
 2. Continue to Week 1: [Week 1: Foundation and first use case](/get-started/trial-week-1.md) to start building your PoC.
 
-3. Set success criteria: Visit [Proof of concept framework](/get-started/trial-poc-framework.md) to define what success looks like for your organization.
-
 :::{tip}
 You can always expand to additional use cases after your initial PoC. Many successful Elastic implementations start with one solution and grow into comprehensive platforms that address multiple needs.
 :::
 
-## Need more guidance?
+## Need more guidance
 
 - [Solutions overview](/get-started/introduction.md): Detailed comparison of all three solutions.
-- [Customer success stories](https://www.elastic.co/customers/success-stories): See how other organizations use Elastic.
+- [Customer success stories](https://www.elastic.co/customers/success-stories): Learn how other organizations use Elastic.
 - [Contact sales](https://www.elastic.co/contact): Speak with a specialist about your specific needs.
 

get-started/trial-getting-started.md

@@ -13,32 +13,32 @@ navigation_title: Get started with Elastic
 
 # Get started with your Elastic trial
 
-Welcome to Elastic! You've started your free trial, and now it's time to explore what Elastic can do for your organization. This guide provides a structured path to help you make the most of your trial period, understand Elastic's capabilities, and build a meaningful proof of concept (PoC) that demonstrates value to your team.
+Welcome to Elastic. You've started your free trial, and now it's time to explore what Elastic can do for your organization. This guide provides a structured path to help you make the most of your trial period, understand Elastic's capabilities, and build a meaningful proof of concept (PoC) that demonstrates value to your team.
 
-By following this guide, you'll:
+By following this guide, you will:
 
 - Set up your Elastic environment in minutes.
 - Choose the right use case for your organization (search, observability, or security).
 - Ingest real data from your systems.
 - Build a working PoC that solves a real problem.
-- Define and measure success metrics to demonstrate ROI.
+- Define and measure success metrics to demonstrate return on investment (ROI).
 - Identify next steps for expanding your implementation.
 
 ## Before you begin
 
-You'll need the following to complete this tutorial:
+You need the following to complete this tutorial:
 
 - Access to your Elastic trial (if you haven't signed up yet, start at [elastic.co/cloud/trial](https://www.elastic.co/cloud/elasticsearch-service/signup)).
 - Basic familiarity with your chosen use case domain (searching data, monitoring systems, or security analysis).
 - Access to data sources you want to connect (applications, logs, metrics, or security events).
 
 :::{tip}
-Set aside focused time blocks to work through this tutorial. You'll get the most value by following the week-by-week structure rather than rushing through everything at once.
+Set aside focused time blocks to work through this tutorial. You get the most value by following the week-by-week structure rather than rushing through everything at once.
 :::
 
 ## Your trial roadmap
 
-This tutorial is designed to fit within your trial period, with clear milestones for each week.
+This tutorial fits within your trial period, with clear milestones for each week.
 
 ### Week 1: Foundation and first use case
 
@@ -58,15 +58,13 @@ Build on your foundation by expanding your PoC and preparing for team evaluation
 
 ## Building your proof of concept
 
-A successful proof of concept (PoC) demonstrates clear value and helps you make an informed decision about adopting Elastic.
-
-**[Proof of concept framework](/get-started/trial-poc-framework.md)**: Learn how to define success criteria, identify key stakeholders, and measure results that matter to your organization.
+A successful proof of concept (PoC) demonstrates clear value and helps you make an informed decision about adopting Elastic. Throughout this tutorial, you'll learn how to define success criteria, identify key stakeholders, and measure results that matter to your organization.
 
 ## Choosing your use case
 
 Not sure which use case is right for you? Refer to **[Choose your use case](/get-started/trial-choose-use-case.md)** to understand the differences between search, observability, and security solutions, and select the best starting point for your needs.
 
-## Need help?
+## Need help
 
 Throughout your trial, you have access to the following resources: