From 7345412a8d64fe00730ddd5f5f40e23b1f2b3443 Mon Sep 17 00:00:00 2001 From: inthelightofthetruth Date: Tue, 20 Jul 2021 21:17:57 -0400 Subject: [PATCH] Grammar Mostly Hey Guys , I fixed (I think) the consistency of the spelling of "open source" Some sentence3s were a bit wordy. Some sentences lacked punctuation that may have contributed to an unclear image in the reader's mind or made for an awkward read.. Hope this helps --- docs/index.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/index.md b/docs/index.md index e88f094..31b645a 100644 --- a/docs/index.md +++ b/docs/index.md @@ -6,11 +6,11 @@ For information about contributing to the Portainer documentation, see [Contribu ## :fontawesome-solid-address-card: About Portainer -Portainer Community Edition 2.0 is the foundation of the Portainer world. With over half a million regular users, it’s a powerful, open-source toolset that allows you to easily build and manage containers in Docker, Swarm, Kubernetes and Azure ACI. +Portainer Community Edition 2.0 is the foundation of the Portainer world. With over half a million regular users, it’s a powerful, open source toolset that allows you to easily build and manage containers in Docker, Docker Swarm, Kubernetes and Azure ACI. -Portainer works by hiding the complexity that makes managing containers hard, behind an easy to use GUI. By negating the need for users to use CLI, write YAML or understand manifests, Portainer makes deploying apps and troubleshooting problems so simple, anyone can do it. +Portainer hides the complexity of managing containers behind an easy to use GUI. By removing the need to use the CLI, write YAML or understand manifests, Portainer makes deploying apps and troubleshooting problems so simple that anyone can do it. -The Portainer development team is here to assist you on your container journey; you can engage with them any time through our community-based support channels. +The Portainer development team is here to assist you on your container journey. You can engage with them any time through our community-based support channels. ## :fontawesome-solid-question-circle: Knowledge Base and FAQs @@ -18,19 +18,19 @@ As the Portainer community continues to grow, we continue to support the communi To streamline our operations and allow us to focus on delivering the right support and features in the right areas at the right time we encourage you to refer to our comprehensive [Knowledge Base](https://support.portainer.io) for any queries you may have. -If you can't find what you're looking for Knowledge Base then please refer to one of the following support channels +If you can't find what you're looking for in our Knowledge Base then please refer to one of the support channels listed below. ## :material-comment-account: Support Channels -Being a free and opensource product, we have been heavily reliant on our community to provide "how to" support to our community, recently we have invested significant time in improving and updating our documentation found on this site and our [YouTube channel](https://www.youtube.com/channel/UC7diMJcrULjDseq5yhSUZgg). While we endeavour to cover as many scenarios as possible there may be some that our documentation doesn’t cover. +As a free and open source product, we have been heavily reliant on our community to provide "how to" support to our community, recently, we have invested significant time in improving and updating our documentation found on this site and our [YouTube channel](https://www.youtube.com/channel/UC7diMJcrULjDseq5yhSUZgg). While we endeavour to cover as many scenarios as possible, there may be some that our documentation doesn’t cover. -* QUESTIONS should be posted to either [Github Issues](https://github.com/portainer/portainer/issues) or the [community Slack channel](https://portainer.slack.com/join/shared_invite/enQtNDk3ODQ5MjI2MjI4LTcwNGYxMWQ5OGViYWZkNDY2ZjY4YTMwMTgzYmU4YmNiOTU0MDcxYmJjNTIyYmQ0MTM5Y2QwNTg3NzNkMTk5MDg#/). While other platforms exist (Reddit, Discord, Stack Overflow) the Portainer team is less active in these. +* QUESTIONS should be posted to either [Github Issues](https://github.com/portainer/portainer/issues) or to the [community Slack channel](https://portainer.slack.com/join/shared_invite/enQtNDk3ODQ5MjI2MjI4LTcwNGYxMWQ5OGViYWZkNDY2ZjY4YTMwMTgzYmU4YmNiOTU0MDcxYmJjNTIyYmQ0MTM5Y2QwNTg3NzNkMTk5MDg#/). While we offer other platforms for questions (Reddit, Discord, Stack Overflow) the Portainer team will be less active in these. -* Suspected BUGS should be posted to Github and will be managed by our support and development teams as appropriate. +* Suspected BUGS should be posted to Github. There they will be appropriately managed by our support and development teams. * VULNERABILITIES should be emailed to [security@portainer.io](mailto:security@portainer.io) and will be dealt with immediately. -* ISSUES IN OUR DOCUMENTATION can be raised through our [Github Documentation Channel](https://github.com/portainer/portainer-docs/issues), or you can follow the user contribution guidelines. +* ISSUES IN OUR DOCUMENTATION can be raised through our [Github Documentation Channel](https://github.com/portainer/portainer-docs/issues), or you can follow the user-contribution guidelines. We will not provide support over email.