icinga.com: Update docs for /community/get-involved -> /community

diff --git a/doc/01-about.md b/doc/01-about.md
index 6397100fe4dd12b375ae680275a76d2d163ac293..efd65b67e39b1c60c716120ced5be5da6c242b2a 100644 (file)
--- a/doc/01-about.md
+++ b/doc/01-about.md
@@ -18,7 +18,7 @@ LICENSE file included in the source package.
 ## Support  <a id="support"></a>
 
 Check the project website at [icinga.com](https://www.icinga.com) for status updates. Join the
-[community channels](https://www.icinga.com/community/get-involved/) for questions
+[community channels](https://icinga.com/community/) for questions
 or ask an Icinga partner for [professional support](https://www.icinga.com/services/support/).
 
 ## Contribute  <a id="contribute"></a>

diff --git a/doc/04-configuring-icinga-2.md b/doc/04-configuring-icinga-2.md
index 61e920126e918bc54122cf082f756b6a3ba9fe89..4d8770ced6d4d7df5a99acc68c610b05113b7146 100644 (file)
--- a/doc/04-configuring-icinga-2.md
+++ b/doc/04-configuring-icinga-2.md
@@ -66,7 +66,7 @@ There is a detailed chapter on [distributed monitoring scenarios](06-distributed
 Please ensure to have read the [introduction](06-distributed-monitoring.md#distributed-monitoring) at first glance.
 
 If you happen to have further questions, do not hesitate to join the
-[community support channels](https://www.icinga.com/community/get-involved/)
+[community support channels](https://icinga.com/community/)
 and ask community members for their experience and best practices.
 
 ## Your Configuration <a id="your-configuration"></a>

diff --git a/doc/05-service-monitoring.md b/doc/05-service-monitoring.md
index 004bf45819bb497520f27c625670b45f7d1cdba4..2ee74e0e960cf016d0f0983247a4b003ddf91c27 100644 (file)
--- a/doc/05-service-monitoring.md
+++ b/doc/05-service-monitoring.md
@@ -93,7 +93,7 @@ For further information on your monitoring configuration read the
 [Monitoring Basics](03-monitoring-basics.md#monitoring-basics) chapter.
 
 If you have created your own `CheckCommand` definition, please kindly
-[send it upstream](https://www.icinga.com/community/get-involved/).
+[send it upstream](https://icinga.com/community/).
 
 ### Plugin API <a id="service-monitoring-plugin-api"></a>
 

diff --git a/doc/06-distributed-monitoring.md b/doc/06-distributed-monitoring.md
index 8bd68d9ffd313d07ebd9a899032884ea3bd375bf..fa1bcdb6775d1089a8531ec19b982ba343657465 100644 (file)
--- a/doc/06-distributed-monitoring.md
+++ b/doc/06-distributed-monitoring.md
@@ -1215,7 +1215,7 @@ If you are eager to start fresh instead you might take a look into the
 
 The following examples should give you an idea on how to build your own
 distributed monitoring environment. We've seen them all in production
-environments and received feedback from our [community](https://www.icinga.com/community/get-involved/)
+environments and received feedback from our [community](https://icinga.com/community/)
 and [partner support](https://www.icinga.com/services/support/) channels:
 
 * Single master with clients.
@@ -1989,7 +1989,7 @@ to make sure that your cluster notifies you in case of failure.
 ## Best Practice <a id="distributed-monitoring-best-practice"></a>
 
 We've put together a collection of configuration examples from community feedback.
-If you like to share your tips and tricks with us, please join the [community channels](https://www.icinga.com/community/get-involved/)!
+If you like to share your tips and tricks with us, please join the [community channels](https://icinga.com/community/)!
 
 ### Global Zone for Config Sync <a id="distributed-monitoring-global-zone-config-sync"></a>
 
@@ -2666,7 +2666,7 @@ These are collected best practices from various community channels.
 
 If you prefer an alternate method, we still recommend leaving all the Icinga 2 features intact (e.g. `icinga2 feature enable api`).
 You should also use well known and documented default configuration file locations (e.g. `zones.conf`).
-This will tremendously help when someone is trying to help in the [community channels](https://www.icinga.com/community/get-involved/).
+This will tremendously help when someone is trying to help in the [community channels](https://icinga.com/community/).
 
 
 ### Silent Windows Setup <a id="distributed-monitoring-automation-windows-silent"></a>

diff --git a/doc/13-addons.md b/doc/13-addons.md
index 1d26de74764900a3096540ab9536ddc0a5756d7d..7a7e81d2283730a967040067e4a5f27f851193e1 100644 (file)
--- a/doc/13-addons.md
+++ b/doc/13-addons.md
@@ -131,7 +131,7 @@ touch with their developers. The Icinga project does not provide a configuration
 yet. Follow the [Icinga Blog](https://www.icinga.com/blog/) for updates on this topic.
 
 If you're looking for puppet manifests, chef cookbooks, ansible recipes, etc. -- we're happy
-to integrate them upstream, so please get in touch with the [Icinga team](https://www.icinga.com/community/get-involved/).
+to integrate them upstream, so please get in touch with the [Icinga team](https://icinga.com/community/).
 
 These tools are currently in development and require feedback and tests:
 

diff --git a/doc/21-development.md b/doc/21-development.md
index 4565fd94b5a74bb36573e334fb1e84cbcfe0b491..c7e54878d5f150d04f4699c71e71818af032ae57 100644 (file)
--- a/doc/21-development.md
+++ b/doc/21-development.md
@@ -167,7 +167,7 @@ running Icinga 2.
     (gdb) handle SIGPIPE nostop noprint pass
     (gdb) r
 
-If you create a [bug report](https://www.icinga.com/community/get-involved/),
+If you create a [bug report](https://icinga.com/community/),
 make sure to attach as much detail as possible.
 
 ### GDB Backtrace from Running Process <a id="development-debug-gdb-backtrace-running"></a>

diff --git a/doc/22-selinux.md b/doc/22-selinux.md
index 0e442ecf3892bd437a3da1b5317ec53bd36cf4e4..9801553ccd7d240d4e3f34ffcdcf1934fafd6078 100644 (file)
--- a/doc/22-selinux.md
+++ b/doc/22-selinux.md
@@ -231,7 +231,7 @@ If you experience any problems while running in enforcing mode try to reproduce
 
 After some feedback Icinga 2 is now running in a enforced domain, but still adds also some rules for other necessary services so no problems should occure at all. But you can help to enhance the policy by testing Icinga 2 running confined by SELinux.
 
-Please add the following information to [bug reports](https://www.icinga.com/community/get-involved/):
+Please add the following information to [bug reports](https://icinga.com/community/):
 
 * Versions, configuration snippets, etc.
 * Output of `semodule -l | grep -e icinga2 -e nagios -e apache`