Better links for manual testing process (#32952)

After merging #32948 I realised the links were pointing to
a sub-section and the name was not encouraging.

This PR fixes it as a very small follow-up.

dev/README_RELEASE_AIRFLOW.md

@@ -690,7 +690,8 @@ Once you install and run Airflow, you should perform any verification you see as
 that the Airflow works as you expected.
 
 Breeze also allows you to easily build and install pre-release candidates including providers by following
-simple instructions described in [TESTING.rst](https://github.com/apache/airflow/blob/main/TESTING.rst#testing-pre-release-packages)
+simple instructions described in
+[Manually testing release candidate packages](https://github.com/apache/airflow/blob/main/TESTING.rst#manually-testing-release-candidate-packages)
 
 # Publish the final Apache Airflow release
 

dev/README_RELEASE_PROVIDER_PACKAGES.md

@@ -688,7 +688,8 @@ is available on PyPI apart from SVN packages, so everyone should be able to inst
 the release candidate version.
 
 Breeze allows you to easily install and run pre-release candidates by following simple instructions
-described in [TESTING.rst](https://github.com/apache/airflow/blob/main/TESTING.rst#testing-pre-release-packages)
+described in
+[Manually testing release candidate packages](https://github.com/apache/airflow/blob/main/TESTING.rst#manually-testing-release-candidate-packages)
 
 But you can use any of the installation methods you prefer (you can even install it via the binary wheels
 downloaded from the SVN).