Update with angeladietz feedback (1)

Author: rmloveland

src/current/v26.2/architecture/replication-layer.md

@@ -116,7 +116,7 @@ Sending data locally using delegated snapshots has the following benefits:
 
 Delegated snapshots are managed automatically by the cluster with no need for user involvement.
 
-To limit the impact of snapshot ingestion on a node with a [provisioned rate]({% link {{ page.version.version }}/cockroach-start.md %}#store) configured for its store, CockroachDB can apply [admission control]({% link {{ page.version.version }}/admission-control.md %}) to snapshot transfer based on disk bandwidth. This allows you to limit the disk impact on foreground workloads on the node. When `kvadmission.store.provisioned_bandwidth` is set to a non-zero value and disk-bandwidth admission control is enabled, snapshot ingestion is subject to this control by default. To disable snapshot-ingest bandwidth control, set the [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) `kvadmission.store.snapshot_ingest_bandwidth_control.enabled` to `false`. The related cluster setting `kvadmission.store.snapshot_ingest_bandwidth_control.min_rate.enabled` keeps snapshot ingestion moving at a minimum rate so it is not starved by other elastic work and can continue to make progress. The [metrics]({% link {{ page.version.version }}/metrics.md %}) `admission.wait_durations.snapshot_ingest` and `admission.admitted_snapshot_bytes` let you observe snapshot-ingest wait time and admitted bytes.
+To limit the impact of snapshot ingestion on a node with a [provisioned rate]({% link {{ page.version.version }}/cockroach-start.md %}#store) configured for its store, CockroachDB can apply [admission control]({% link {{ page.version.version }}/admission-control.md %}) to snapshot transfer based on disk bandwidth. This allows you to limit the disk impact on foreground workloads on the node. When `kvadmission.store.provisioned_bandwidth` is set to a non-zero value and disk-bandwidth admission control is enabled (via `admission.disk_bandwidth_tokens.elastic.enabled`), snapshot ingestion is subject to this control by default. To disable snapshot-ingest bandwidth control, set the [cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}) `kvadmission.store.snapshot_ingest_bandwidth_control.enabled` to `false`. The related cluster setting `kvadmission.store.snapshot_ingest_bandwidth_control.min_rate.enabled` keeps snapshot ingestion moving at a minimum rate so it is not starved by other elastic work and can continue to make progress. The [metrics]({% link {{ page.version.version }}/metrics.md %}) `admission.wait_durations.snapshot_ingest` and `admission.admitted_snapshot_bytes` let you observe snapshot-ingest wait time and admitted bytes.
 
 ### Leases