Update container.md

[azarboon]

Describe your changes

Marc Brooker has written a blog post explaining that "container" means different thing to different people, and that it should be checked whether audience and narrator use the same definition. Below are his four suggested definition. Given the authority of CNCF, I suggest this nuance to be mentioned. So readers are more informed and take cautionary acts to ensure they are synced with their audience. I've added it.

• An approach to packaging an application along with its dependencies (sometimes a whole operating system user space), that can then run on a minimal runtime environment with a clear contract.
• A set of development, deployment, architectural, and operational approaches built around applications packaged this way.
• A set of operational, security, and performance isolation tools that allow multiple applications to share an operating system without interfering with each other. On Linux, this tools include chroot, cgroups, namespaces, seccomp, and others.
• A set of implementations of these practices (the proper nouns, Docker, Kubernetes, ECS, etc).

Related issue number or link (ex: resolves #issue-number)

Checklist before opening this PR (put x in the checkboxes)

• This PR does not contain plagiarism
  • don’t copy other people’s work unless you are quoting and contributing it to them.
• I have signed off on all commits
  • signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

[netlify]

✅ Deploy Preview for cncfglossary ready!

Name	Link
🔨 Latest commit	91dc9fa
🔍 Latest deploy log	https://app.netlify.com/sites/cncfglossary/deploys/670a18d85fa17e00086fc766
😎 Deploy Preview	https://deploy-preview-3321--cncfglossary.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[iamNoah1]

@azarboon thanks for the contribution. Here, as well as in your other contributions I am not sure if it really adds value.

The Glossary aims for simple straight forward definitions of terms that can understood also by non tech people. The fact the terms are overloaded and people might have different definitions is something that is true for a lot of terms. I don't know if it adds any value to point that out.

But I am also happy to hear different opinions. @seokho-son @jihoon-seo @nate-double-u

[a-mccarthy]

completely new to this project, but i'd +1 @iamNoah1 comment

The Glossary aims for simple straight forward definitions of terms that can understood also by non tech people. The fact the terms are overloaded and people might have different definitions is something that is true for a lot of terms. I don't know if it adds any value to point that out.

I'm not sure it makes sense to add this comment to every term in the glossary. But it might make sense to add a "How to use this Glossary" section somewhere that elaborates on the glossary's founding principle to keep terms to their simplest definition and what to consider when a reader wants to use a term or learn more about a given term beyond the glossary. (please disregard this comment if this content is already available in the docs 😄)