diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index aa39f0c550..64edf1b54d 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -1096,10 +1096,10 @@ back_pressure_strategy:
 
 # Coalescing Strategies #
 # Coalescing multiples messages turns out to significantly boost message processing throughput (think doubling or more).
-# On bare metal, the floor for packet processing throughput is high enough that many applications won’t notice, but in
+# On bare metal, the floor for packet processing throughput is high enough that many applications won't notice, but in
 # virtualized environments, the point at which an application can be bound by network packet processing can be
-# surprisingly low compared to the throughput of task processing that is possible inside a VM. It’s not that bare metal
-# doesn’t benefit from coalescing messages, it’s that the number of packets a bare metal network interface can process
+# surprisingly low compared to the throughput of task processing that is possible inside a VM. It's not that bare metal
+# doesn't benefit from coalescing messages, it's that the number of packets a bare metal network interface can process
 # is sufficient for many applications such that no load starvation is experienced even without coalescing.
 # There are other benefits to coalescing network messages that are harder to isolate with a simple metric like messages
 # per second. By coalescing multiple tasks together, a network thread can process multiple messages for the cost of one