fix

Author: amychisholm03

lib/samplers/README.md

@@ -68,9 +68,7 @@ distributed_tracing:
 
 ## Solution
 
-There are three sampler modes, each with three sampler sections, resulting in potentially nine different sampling decisions that the agent would have to support.
-
-We create a new `Sampler` instance (`AdaptiveSampler`, `AlwaysOnSampler`, `AlwaysOffSampler`, or `TraceIdRatioBasedSampler`, defined in this folder) for each sampler modes' section, resulting in 9 samplers.
+There are three sampler modes, each with three sampler sections, resulting in potentially nine different sampling decisions that the agent would have to support. We create a new `Sampler` instance (`AdaptiveSampler`, `AlwaysOnSampler`, `AlwaysOffSampler`, or `TraceIdRatioBasedSampler`, defined in this folder) for each of these sampler modes' sections.
 
 `agent.sampler` would be defined as:
 
@@ -87,6 +85,6 @@ These fields currently exist (before core tracing was implemented); `agent.sampl
 * `agent.sampler.remoteParentSampled`
 * `agent.sampler.remoteParentNotSampled`
 
-These samplers have a `applySamplingDecision({transaction})` function, which `Transaction` calls (in `lib/transaction/index.js`) to updated its `sampled` field and therefore its `priority`.
+These samplers have a `applySamplingDecision({transaction})` function, which `Transaction` calls (in `lib/transaction/index.js`) to update its `sampled` field and therefore its `priority`.
 
 Unlike the other samplers, the `AdaptiveSampler` must share state with other `AdaptiveSamplers` with the same `sampling_target`, which complicates our seperate sampler instances approach. This will be fixed shortly, and this document will be updated to describe that solution.