Update envoy-proxy-configuration.md
@@ -71,7 +71,7 @@ Additionally, the cell rep configures the Envoy proxy to bind its administrative
Integrating Envoy into Cloud Foundry for route integrity and other use cases does not come for free. Each Envoy proxy process currently runs in the same container as the application process and so itself uses memory inside the application instance's memory quota. Consequently, operators will likely be interested in compensating for this overhead to reduce the incidence of out-of-memory errors inside application containers, and can do so by setting the `containers.proxy.additional_memory_allocation_mb` property on the `rep` job.
-This property instructs the cell rep to increase the memory quota of all containers by the given amount. For example, if `containers.proxy.additional_memory_allocation_mb` is set to `16` and a container is scheduled on the cell with a memory limit of 256 MB, the actual container effective memory limit will be 256 + 12 = 268 MB. Please note that the cell rep will not overcommit its memory as a result of setting the bosh property, and operators opting into this mode should make sure that they have enough additional memory.
+This property instructs the cell rep to increase the memory quota of all containers by the given amount. For example, if `containers.proxy.additional_memory_allocation_mb` is set to `16` and a container is scheduled on the cell with a memory limit of 256 MB, the actual container effective memory limit will be 256 + 16 = 272 MB. Please note that the cell rep will not overcommit its memory as a result of setting the bosh property, and operators opting into this mode should make sure that they have enough additional memory.
Container memory usage metrics sent through the Loggregator system and exposed on the cell rep's container metrics API endpoint are rescaled linearly to fit within the externally requested quota, to reduce confusion about the source of out-of-memory errors.
