diff --git a/website/docs/guides/migration_guide_alert_conditions.html.markdown b/website/docs/guides/migration_guide_alert_conditions.html.markdown
index e767a09a0..0a479c270 100644
--- a/website/docs/guides/migration_guide_alert_conditions.html.markdown
+++ b/website/docs/guides/migration_guide_alert_conditions.html.markdown
@@ -12,7 +12,11 @@ Certain subtypes of Alert Conditions (Synthetics Alert Condition and Infra Alert
 
 Users wanting to migrate alert conditions will need to make a few adjustments to their configuration, by following the examples outlined below.
 
-### newrelic_synthetics_alert_condition
+### Migrating from Synthetics Alert Conditions to NRQL Alert Conditions
+
+The following example illustrates changing over to an NRQL-based alert condition using the [newrelic_nrql_alert_condition](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/nrql_alert_condition) resource from a Synthetics alert condition, i.e. [newrelic_synthetics_alert_condition](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/nrql_alert_condition).
+
+Below example also illustrates how argument monitor_id in synthetic alert condition should be inserted in NRQL over syntheticCheck after migration.
 
 Example newrelic_synthetics_alert_condition:
 ```
@@ -58,7 +62,13 @@ resource "newrelic_nrql_alert_condition" "foo" {
 }
 ```
 
-### newrelic_infra_alert_condition: High disk usage
+### Migrating from Infra Alert Conditions to NRQL Alert Conditions
+
+The following examples illustrates changing over to an NRQL-based alert condition using the [newrelic_nrql_alert_condition](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/nrql_alert_condition) resource from a Infra alert condition, i.e. [newrelic_infra_alert_condition](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/infra_alert_condition).
+
+#### newrelic_infra_alert_condition: High disk usage
+
+The following example illustrates changing an Infra alert condition for high disk usage to an NRQL-based alert condition.
 
 Example newrelic_infra_alert_condition:
 ```
@@ -126,7 +136,9 @@ resource "newrelic_nrql_alert_condition" "foo" {
 }
 ```
 
-### newrelic_infra_alert_condition: High db connection count
+#### newrelic_infra_alert_condition: High db connection count
+
+The following example illustrates changing an Infra alert condition for high DB connection count to an NRQL-based alert condition.
 
 Example newrelic_infra_alert_condition:
 ```
@@ -182,7 +194,9 @@ resource "newrelic_nrql_alert_condition" "foo" {
 }
 ```
 
-### newrelic_infra_alert_condition: Process not running
+#### newrelic_infra_alert_condition: Process not running
+
+The following example illustrates changing an Infra alert condition for process not running to an NRQL-based alert condition.
 
 Example newrelic_infra_alert_condition:
 ```
@@ -235,7 +249,9 @@ resource "newrelic_nrql_alert_condition" "foo" {
 }
 ```
 
-### newrelic_infra_alert_condition: Host not reporting
+#### newrelic_infra_alert_condition: Host not reporting
+
+The following example illustrates changing an Infra alert condition for host not reporting to an NRQL-based alert condition.
 
 Example newrelic_infra_alert_condition:
 ```
diff --git a/website/docs/r/infra_alert_condition.html.markdown b/website/docs/r/infra_alert_condition.html.markdown
index 843534ff0..f31c638b1 100644
--- a/website/docs/r/infra_alert_condition.html.markdown
+++ b/website/docs/r/infra_alert_condition.html.markdown
@@ -10,7 +10,7 @@ description: |-
 
 Use this resource to create and manage Infrastructure alert conditions in New Relic.
 
--> **WARNING:** The `newrelic_infra_alert_condition` resource is deprecated and will be removed in the next major release. The resource [newrelic_nrql_alert_condition](nrql_alert_condition.html) would be a preferred alternative to configure alert conditions - in most cases, feature parity can be achieved with a NRQL query.
+-> **WARNING:** The `newrelic_infra_alert_condition` resource is deprecated and will be removed in the next major release. The resource [newrelic_nrql_alert_condition](nrql_alert_condition.html) would be a preferred alternative to configure alert conditions - in most cases, feature parity can be achieved with a NRQL query.For more details and examples on moving away from Infra alert conditions to the NRQL based alternative, please check out [these](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/guides/migration_guide_alert_conditions#migrating-from-infra-alert-conditions-to-nrql-alert-conditions) examples.
 
 ## Example Usage
 
diff --git a/website/docs/r/synthetics_alert_condition.html.markdown b/website/docs/r/synthetics_alert_condition.html.markdown
index d9f571e91..f91088dfc 100644
--- a/website/docs/r/synthetics_alert_condition.html.markdown
+++ b/website/docs/r/synthetics_alert_condition.html.markdown
@@ -10,7 +10,7 @@ description: |-
 
 Use this resource to create and manage synthetics alert conditions in New Relic.
 
--> **WARNING:** The `newrelic_synthetics_alert_condition` resource is deprecated and will be removed in the next major release. The resource [newrelic_nrql_alert_condition](nrql_alert_condition.html) would be a preferred alternative to configure alert conditions - in most cases, feature parity can be achieved with a NRQL query.
+-> **WARNING:** The `newrelic_synthetics_alert_condition` resource is deprecated and will be removed in the next major release. The resource [newrelic_nrql_alert_condition](nrql_alert_condition.html) would be a preferred alternative to configure alert conditions - in most cases, feature parity can be achieved with a NRQL query.For more details and examples on moving away from Synthetics alert conditions to the NRQL based alternative, please check out [this](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/guides/migration_guide_alert_conditions#migrating-from-synthetics-alert-conditions-to-nrql-alert-conditions) example.
 
 ## Example Usage