From b8a82d2f19b3e2012b399bd19b7255cae5c97ee7 Mon Sep 17 00:00:00 2001
From: sreallymatt <106555974+sreallymatt@users.noreply.github.com>
Date: Tue, 10 Dec 2024 07:34:29 -0700
Subject: [PATCH] Address comments

---
 contributing/topics/guide-breaking-changes.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/contributing/topics/guide-breaking-changes.md b/contributing/topics/guide-breaking-changes.md
index 679cba6b3774..4283860b12e1 100644
--- a/contributing/topics/guide-breaking-changes.md
+++ b/contributing/topics/guide-breaking-changes.md
@@ -166,7 +166,7 @@ The following example follows a fictional resource that will have the following
          },
       }
    
-      if !features.FivePointOhBeta {
+      if !features.FivePointOhBeta() {
          args["enable_scaling"] = &pluginsdk.Schema{
             Type:     pluginsdk.TypeBool,
             Optional: true,
@@ -336,7 +336,7 @@ Terraform will perform the following actions:
 Plan: 0 to add, 1 to change, 0 to destroy.
 ```
 
-This is a breaking change as Terraform should not trigger a plan between minor version upgrades. Instead, what we can do is add a TODO next to the `Default` tag to update the default value in the next major version of the provider or mark the field as Required if that default value is going to continue to change in the future:
+This is a breaking change as Terraform should not trigger a plan between minor version upgrades. Instead, what we can do is use the major release feature flag as shown in the example below or mark the field as Required if that default value is going to continue to change in the future:
 
 ```go
 func (r SparkResource) Arguments() map[string]*pluginsdk.Schema{