From 2ef4f315c78ef9cecbc06cbf0062eeb50d0464c1 Mon Sep 17 00:00:00 2001
From: Pierre Le Noan <144696725+pierreln-dd@users.noreply.github.com>
Date: Thu, 5 Dec 2024 13:47:17 +0100
Subject: [PATCH 1/3] Update sql_deadlock.md

---
 content/en/database_monitoring/guide/sql_deadlock.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/en/database_monitoring/guide/sql_deadlock.md b/content/en/database_monitoring/guide/sql_deadlock.md
index b62b8aca6fd..07aa3ccf9c6 100644
--- a/content/en/database_monitoring/guide/sql_deadlock.md
+++ b/content/en/database_monitoring/guide/sql_deadlock.md
@@ -14,6 +14,7 @@ further_reading:
 
 The Deadlock view enables you to explore deadlock events in your SQL Server database.
 A deadlock occurs when two or more processes are unable to proceed because each is waiting for the other to release resources.
+
 This guide assumes that Database Monitoring has been configured for your [SQL Server][1].
 
 ## Before you begin
@@ -49,7 +50,7 @@ Supported Agent versions
   GO
 ```
 
-2. In the Datadog Agent, enable deadlocks in `sqlserver.d/conf.yaml`.
+2. In addition to the [DBM for SQL Server setup][1]. In the Datadog Agent, enable deadlocks in `sqlserver.d/conf.yaml`.
 ```yaml
   deadlocks_collection:
       enabled: true

From 1d983ca9b1746d1b219394397f4e6393a0ff20c1 Mon Sep 17 00:00:00 2001
From: Pierre Le Noan <144696725+pierreln-dd@users.noreply.github.com>
Date: Fri, 6 Dec 2024 09:52:33 +0100
Subject: [PATCH 2/3] Update
 content/en/database_monitoring/guide/sql_deadlock.md

Co-authored-by: Sandra (neko) <165049174+neko-dd@users.noreply.github.com>
---
 content/en/database_monitoring/guide/sql_deadlock.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/en/database_monitoring/guide/sql_deadlock.md b/content/en/database_monitoring/guide/sql_deadlock.md
index 07aa3ccf9c6..fdf8866ea06 100644
--- a/content/en/database_monitoring/guide/sql_deadlock.md
+++ b/content/en/database_monitoring/guide/sql_deadlock.md
@@ -15,10 +15,11 @@ further_reading:
 The Deadlock view enables you to explore deadlock events in your SQL Server database.
 A deadlock occurs when two or more processes are unable to proceed because each is waiting for the other to release resources.
 
-This guide assumes that Database Monitoring has been configured for your [SQL Server][1].
-
 ## Before you begin
 
+You must configure Database Monitoring for your [SQL Server][1] before following the steps in this guide.
+
+
 Supported databases
 : SQL Server
 

From f9668396f614ac019d22248c64d7fe15e1fbc903 Mon Sep 17 00:00:00 2001
From: Pierre Le Noan <144696725+pierreln-dd@users.noreply.github.com>
Date: Fri, 6 Dec 2024 09:52:50 +0100
Subject: [PATCH 3/3] Update
 content/en/database_monitoring/guide/sql_deadlock.md

Co-authored-by: Sandra (neko) <165049174+neko-dd@users.noreply.github.com>
---
 content/en/database_monitoring/guide/sql_deadlock.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/database_monitoring/guide/sql_deadlock.md b/content/en/database_monitoring/guide/sql_deadlock.md
index fdf8866ea06..3018b7e0aa7 100644
--- a/content/en/database_monitoring/guide/sql_deadlock.md
+++ b/content/en/database_monitoring/guide/sql_deadlock.md
@@ -51,7 +51,7 @@ Supported Agent versions
   GO
 ```
 
-2. In addition to the [DBM for SQL Server setup][1]. In the Datadog Agent, enable deadlocks in `sqlserver.d/conf.yaml`.
+2. In the Datadog Agent, enable deadlocks in `sqlserver.d/conf.yaml`.
 ```yaml
   deadlocks_collection:
       enabled: true