Incorporated feedback

* Updated the title for the API doc

* Removed the "Dashboard Analysis" and "Create Synthetic Monitoring" use cases and replaced it with "What happened previously"

* Added a callout in the API doc, calling out the required permission and things to keep in mind.

Author: tejaswaroop-nr

src/content/docs/agentic-ai/knowledge-integration/overview.mdx

@@ -19,7 +19,7 @@ By setting up the New Relic AI knowledge connector, you can expect tangible outc
 
 ## Use cases and value
 
-The following examples show how the knowledge connector integration helps the New Relic AI tools tackle challenges like fragmented documentation, slow incident response, and missing business context by surfacing relevant information.
+The following examples show how the knowledge connector integration helps tackle challenges like fragmented documentation and slow incident response by surfacing relevant information.
 
 <CollapserGroup>
 <Collapser id="retro-docsearch-tool" title="Retro DocSearch">
@@ -33,27 +33,14 @@ The knowledge connector integrates all of these disparate sources, transforming
 * Identify the names of the experts or teams who solved it before.
 
 </Collapser>
-<Collapser id="dashboard-analysis-tool" title="Dashboard Analysis">
+<Collapser id="what-happened-previously" title="What happened previously">
 
-While the Dashboard Analysis tool provides key insights, its analysis is limited to the data received by the dashboard. It lacks crucial business context, making it difficult to understand the true impact of an issue.
+When an IT issue reoccurs, you'll often have to spend valuable time trying to figure out if it has happened before. Your historical context is often scattered across separate retrospective or postmortem documents, which can make it difficult to quickly find the information you need to resolve a recurring incident.
 
-The knowledge connector integration grounds the Dashboard Analysis tool in your company's unique knowledge, acting as a bridge between raw telemetry and your internal documentation. This allows the tool to:
+By leveraging RAG, the New Relic AI platform stores information from your existing retrospective or postmortem documents for future reference. This helps you save valuable time during an incident. The What happened previously widget, with RAG implementation, allows you to:
 
-* Explain the business impact using indexed documents that define key business metrics.
-* Curate suggestions based on internal runbooks to provide context-specific actionable steps.
-* Explain historical context by referencing an indexed Jira ticket or internal document.
-
-</Collapser>
-
-<Collapser id="synthetic-monitor-creation" title="Create Synthetic Monitoring">
-
-This tool generates a basic synthetic monitor creation script, but it lacks an understanding of your organization's unique standards and proprietary information. This creates manual work to ensure compliance and inject authentication tokens.
-
-The knowledge connector integration elevates the tool by giving it access to your company's internal documents. This allows the tool to:
-
-* Automate standardization by applying your company’s rules to the generated script.
-* Inject specific non-public information from an indexed runbook or wiki into the monitor's configuration.
-* Automatically link the monitor to the relevant runbooks so troubleshooting context is attached to the alert.
+* Quickly find relevant information and learn from previous incidents.
+* Get a summary of similar past issues, along with links to the retrospective documents for detailed analysis.
 
 </Collapser>
 </CollapserGroup>

src/content/docs/apis/nerdgraph/examples/nerdgraph-rag.mdx

@@ -1,5 +1,5 @@
 ---
-title: "NerdGraph tutorial: Configure RAG tools and documents"
+title: "NerdGraph tutorial: Set up RAG integration"
 metaDescription: Enhance New Relic AI with RAG (Retrieval Augmented Generation)
 redirects:
   - /docs/agentic-ai/knowledge-integration/apis-and-communication-protocol
@@ -18,6 +18,12 @@ After adding your documents, you will create a relationship to associate them wi
 
 To learn more about the knowledge connector, refer to [New Relic AI Knowledge connector](/docs/agentic-ai/knowledge-integration/overview).
 
+<Callout variant="important">
+ Before performing the following steps:
+ * Ensure that you have "Org Product Admin" permissions.
+ * All indexed documents are visible to all users within your organization. Make sure the documents you index comply with your internal policies, and do not upload sensitive or private data.
+</Callout>
+
 To start indexing your content and benefit from the knowledge connector with New Relic AI, follow these mentioned steps:
 
 ## Create your RAG tool [#create-your-rag-tool]
@@ -42,8 +48,6 @@ Organization ID is required to perform mutations and queries in NerdGraph when s
 </Collapser>
 <Collapser id = "create-rag-tool" title = "Create a RAG tool">
 
-Before performing this step, ensure you have "Org Product Admin" permissions.
-
 A RAG tool acts as a specialized container for organizing related documents and resources in New Relic. A clear name and accurate description for your RAG tools helps the LLM select the right tool for each prompt, ensuring relevant and context-aware responses.
 
 To create a new RAG tool in your New Relic account, run the following `entityManagementCreateRagTool` mutation:
@@ -125,10 +129,6 @@ You should save the `id` returned as you'll need it in later steps to link docum
 
 <Collapser id = "upload-document" title = "Upload a document via the Blob API">
 
-<Callout variant="important">
-  All indexed documents are visible to all users within your organization. Make sure the documents you index comply with your internal policies, and do not upload sensitive or private data.
-</Callout>
-
 ### The Blob API and its purpose
 The Blob API is a New Relic service designed for uploading files, such as documentation and runbooks, to your account. NerdGraph is optimized for structured data queries and mutations and not for efficient transfer of files, so the Blob API is required for uploading documents.