docs(memory): tenant sub-namespaces inherit the pool root's LimitRange #806

content/en/docs/next/operations/configuration/system-memory-limits.md (section "What Cozystack does") says that a tenant namespace gets a default of its own only from the tenant chart's tenant-range-limits, rendered only when resourceQuotas is configured on the tenant. Once cozystack/cozystack#5265 is merged, that is no longer the only source.

With hierarchical quotas, a sub-tenant that declares no resourceQuotas shares its parent's budget and receives a controller-owned tenant-quota-allocated ResourceQuota. When that quota bounds limits.cpu or limits.memory, cozystack-controller now copies the pool root's tenant-range-limits into the sub-tenant as tenant-range-limits-allocated, keeps it in step with the root, and removes it when the sub-tenant leaves the pool or its quota no longer bounds a compute limit. A tenant namespace can therefore carry container defaults without declaring resourceQuotas itself.

The paragraph should mention that second source. It is the same paragraph #797 edits for GPU-only budgets, so the two changes should be made together or one after the other. The v1.7 copy of the page only needs the change if #5265 is backported.