Conclusion: future: <DB, etc>aaS

Conclusion: future: CRI hardening

Conclusion: future: add NetworkPolicy

Architecture: wordings: use tenancy

we do already introduced it via multi-tenancy, and it is more precise

Conclusion: outline future works

test push

unify ref styles

enrich refs

Architecture: more consistent subsection titles

remove topic

Architecture: revisit

Architecture: revisit until cel

lower case v

revisit Introduction, Backgrounds, RelatedWorks

Architecture: provisioner tests

Architecture: LimitRange

Architecture: ResourceQuota: cheap admission control and object limit

Architecture: more ResourceQuota intro

un-verbify kube-apiserver

turns out to be a little over-verbing, let's leave it to only code,
fields and libraries

Architecture: ResourceQuota: whatis