Fix links

README.md

@@ -87,7 +87,7 @@ Let's prevent working against each other!
     and generating HTML go into the **theme**
 -   Business logic (e.g. processing input from visitors) goes into **plugins**
 -   Please adhere to a coding standard of **your choice**
--   Please avoid [discouraged functions](https://github.com/szepeviktor/debian-server-tools/blob/master/webserver/laravel/phpcs.xml#L18)
+-   Please avoid [discouraged functions](https://github.com/szepeviktor/phpcs-psr-12-neutron-hybrid-ruleset/blob/master/PSR12NeutronRuleset/ruleset.xml#L11)
 -   We run static analysis on all source code
 -   PSR-4 autoloading is suggested (no need for `require` and custom class autoloading)
 -   WordPress core is installed in a separate subdirectory

WordPress-OOP.md

@@ -32,8 +32,6 @@
 
 -   [iron-bound-designs/psr-14-wp](https://github.com/iron-bound-designs/psr-14-wp)
     PSR-14 implementation for WordPress.
--   [inpsyde/wp-events](https://github.com/inpsyde/wp-events)
-    PSR-14 compliant wrapper.
 -   [szepeviktor/persistent-admin-notices](https://github.com/szepeviktor/wordpress-persistent-admin-notices)
     Persistent admin notices for WordPress.
 -   [szepeviktor/acf-get](https://github.com/szepeviktor/acf-get)

WordPress-security.md

@@ -33,7 +33,7 @@
 ## Server-side
 
 -   HTTPS websites receive less attacks: force HTTPS ([HSTS](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security))
--   Block known hostile networks ([myattackers-ipset](/security/myattackers-ipsets))
+-   Block known hostile networks ([myattackers-ipset](https://github.com/szepeviktor/debian-server-tools/tree/master/security/myattackers-ipsets))
 -   Preventively block vulnerability scanners ([WAF for WordPress](https://github.com/szepeviktor/waf4wordpress))
 -   Restrict access to core, theme and plugin files and directories
     ([wordpress.inc.conf](https://github.com/szepeviktor/debian-server-tools/blob/master/webserver/apache-conf-available/wordpress.inc.conf))