docs: fix or remove dead links

docs/README.md

@@ -1542,7 +1542,7 @@ $ http --ssl=ssl3 https://vulnerable.example.org
 ### SSL ciphers
 
 You can specify the available ciphers with `--ciphers`.
-It should be a string in the [OpenSSL cipher list format](https://www.openssl.org/docs/man1.1.0/man1/ciphers.html).
+It should be a string in the [OpenSSL cipher list format](https://docs.openssl.org/3.5/man1/openssl-ciphers/).
 
 ```bash
 $ http --ciphers=ECDHE-RSA-AES128-GCM-SHA256 https://pie.dev/get

docs/installation/methods.yml

@@ -106,7 +106,7 @@ tools:
     note: Also works for other Arch-derived distributions like ArcoLinux, EndeavourOS, Artix Linux, etc.
     links:
       homepage: https://archlinux.org/pacman/
-      package: https://archlinux.org/packages/community/any/httpie/
+      package: https://archlinux.org/packages/extra/any/httpie/
     commands:
       install:
         - pacman -Syu httpie

docs/packaging/README.md

@@ -21,13 +21,13 @@ The overall release process starts simple:
 4. Make a GitHub release (by copying the text in `CHANGELOG.md`)
 5. Push that release to PyPI (dispatch the `Release PyPI` GitHub action).
 6. Once PyPI is ready, push the release to the Snap, Homebrew and Chocolatey with their respective actions.
-7. Go to the [`httpie/debian.httpie.io`](https://github.com/httpie/debian.httpie.io) repo and trigger the package index workflow.
+7. Go to the `httpie/debian.httpie.io` repo and trigger the package index workflow.
 
 ## Company-specific tasks
 
 - Blank the `master_and_released_docs_differ_after` value in [config.json](https://github.com/httpie/cli/blob/master/docs/config.json).
 - Update the [contributors list](../contributors).
-- Update the HTTPie version bundled into [Termible](https://termible.io/) ([example](https://github.com/httpie/termible/pull/1)).
+- Update the HTTPie version bundled into [Termible](https://termible.io/).
 
 ## Finally, spread dowstream
 

docs/packaging/linux-arch/README.md

@@ -15,7 +15,7 @@ We will discuss setting up the environment, installing development tools, instal
 
 Note: Sending patches downstream does not seem easy. We failed to find where is located the package file on <https://gitlab.archlinux.org>. So we are relying on the last maintainer, daurnimator, and it works pretty well so far.
 
-Check <https://archlinux.org/packages/community/any/httpie/> and if the version is outdated, simply [report it](https://archlinux.org/packages/community/any/httpie/flag/).
+Check <https://archlinux.org/packages/extra/any/httpie/> and if the version is outdated, simply report it there.
 
 ## Hacking
 

docs/packaging/linux-debian/README.md

@@ -20,7 +20,7 @@ command (due to the underlying `httpie cli plugins` interface) explicitly depend
 The [`Release as Standalone Linux Binary`](https://github.com/httpie/cli/actions/workflows/release-linux-standalone.yml) will be automatically
 triggered when a new release is created, and it will submit the `.deb` package as a release asset.
 
-For making that asset available for all debian users, the release manager needs to go to the [`httpie/debian.httpie.io`](https://github.com/httpie/debian.httpie.io) repo
-and trigger the [`Update Index`](https://github.com/httpie/debian.httpie.io/actions/workflows/update-index.yml) action. It will automatically
-scrape all new debian packages from the release assets, properly update the indexes and create a new PR ([an example](https://github.com/httpie/debian.httpie.io/pull/1))
+For making that asset available for all debian users, the release manager needs to go to the `httpie/debian.httpie.io` repo
+and trigger the `Update Index` action. It will automatically
+scrape all new debian packages from the release assets, properly update the indexes and create a new PR
 which then will become active when merged.