From 68d0112560216e4f944a73fae4520e7d111c50ee Mon Sep 17 00:00:00 2001
From: Hannah Ramadan <76922290+hannahramadan@users.noreply.github.com>
Date: Thu, 16 Jan 2025 14:31:56 -0800
Subject: [PATCH] Apply suggestions from code review

---
 CHANGELOG.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 23242a2c5c..c25db7fb65 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,9 +6,9 @@
 
   The agent now supports Ruby 3.4.0. We've made incremental changes throughout the preview stage to reach compatibility. This release includes an update to the Thread Profiler for compatibility with Ruby 3.4.0's new backtrace format. [Issue#2992](https://github.com/newrelic/newrelic-ruby-agent/issues/2992) [PR#2997](https://github.com/newrelic/newrelic-ruby-agent/pull/2997)
 
-- **Feature: Use the agent deployment received from Kubernetes APM auto-attach**
+- **Feature: Kubernetes APM auto-attach - new agent version precedent**
 
-  Previously, an existing deployment Ruby agent would continue be used if re-installing the agent via [Kubernetes APM auto-attach](https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/). Now, the agent version installed from Kubernetes APM auto-attach will be deployed and any existing deployment will be removed. [PR#3018](https://github.com/newrelic/newrelic-ruby-agent/pull/3018)
+  Previously, when a customer installed the Ruby agent via [Kubernetes APM auto-attach](https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/) and also had the Ruby agent listed in their `Gemfile`, the agent version in `Gemfile` would take precedence. Now, the agent version installed by auto-attach takes priority. [PR#3018](https://github.com/newrelic/newrelic-ruby-agent/pull/3018)
 
 - **Bugfix: Stop emitting inaccurate debug-level log about deprecated configuration options**