docs: fix links

Author: hynek

docs/frameworks.md

@@ -74,7 +74,7 @@ request_started.connect(bind_request_details, app)
 
 ## OpenTelemetry
 
-The [Python OpenTelemetry SDK](https://opentelemetry.io/docs/instrumentation/python/) offers an easy API to get the current span, so you can enrich your logs with a straight-forward processor:
+The [Python OpenTelemetry SDK](https://opentelemetry.io/docs/languages/python/) offers an easy API to get the current span, so you can enrich your logs with a straight-forward processor:
 
 ```python
 from opentelemetry import trace

docs/logging-best-practices.md

@@ -82,9 +82,9 @@ All you have to do is to tell [Logstash] either that your log entries are prepen
 
 ### Graylog
 
-[Graylog](https://www.graylog.org/) goes one step further.
+[Graylog](https://graylog.org/) goes one step further.
 It not only supports everything those above do (and then some); you can also directly log JSON entries towards it -- optionally even through an AMQP server (like [RabbitMQ](https://www.rabbitmq.com/)) for better reliability.
-Additionally, [Graylog's Extended Log Format](https://docs.graylog.org/docs/gelf) (GELF) allows for structured data which makes it an obvious choice to use together with *structlog*.
+Additionally, [Graylog's Extended Log Format](https://go2docs.graylog.org/current/getting_in_log_data/gelf.html) (GELF) allows for structured data which makes it an obvious choice to use together with *structlog*.
 
 
 [elasticsearch]: https://www.elastic.co/elasticsearch