Remove links to 6.2-SNAPSHOT

Spring-Framework-6.2-Release-Notes.md

@@ -87,7 +87,7 @@ class MyConfiguration {
 If no other `MyService` bean is defined, `defaultMyService` is used.
 Otherwise, the container will pick transparently the one that’s been defined externally.
 
-[See the dedicated section in the reference documentation.](https://docs.spring.io/spring-framework/reference/6.2-SNAPSHOT/core/beans/annotation-config/autowired-qualifiers.html#page-title)
+[See the dedicated section in the reference documentation.](https://docs.spring.io/spring-framework/reference/core/beans/annotation-config/autowired-qualifiers.html)
 
 ### Background bean initialization
 
@@ -173,7 +173,7 @@ See [#32676](https://github.com/spring-projects/spring-framework/issues/32676).
 
 Spring MVC and WebFlux support rendering multiple views in one request, or to create a stream of rendered views. This helps to support HTML-over-the-wire libraries such as htmx.org and @hotwired/turbo. 
 
-See [HTML Fragments](https://docs.spring.io/spring-framework/reference/6.2-SNAPSHOT/web/webmvc-view/mvc-fragments.html) in the reference documentation.
+See [HTML Fragments](https://docs.spring.io/spring-framework/reference/web/webmvc-view/mvc-fragments.html) in the reference documentation.
 
 
 ### Content negotiation for `@ExceptionHandler` methods
@@ -200,7 +200,7 @@ Here, automated clients will get a JSON response, while browsers will display an
 
 ### URL Parsing
 
-Two new URL parser implementations replace the regular expression based parsing that led to vulnerability reports such as [CVE-2024-22262](https://spring.io/security/cve-2024-22262) and others after it. The parser implementation used by default follows closely RFC 3986 syntax, in effect expecting URL's to be well formed. The other parser follows the [URL Living URL standard](https://url.spec.whatwg.org), and provides lenient handling of a wide range of user typed URL's, which allows parsing URL's in the same way that browsers do, and is important in scenarios where a server application parses a user provided URL that is then returned to and may be used by a browser (e.g. redirect or as a link in HTML). See [URI Parsing](https://docs.spring.io/spring-framework/reference/6.2-SNAPSHOT/web/webmvc/mvc-uri-building.html#uri-parsing) in the reference documentation.
+Two new URL parser implementations replace the regular expression based parsing that led to vulnerability reports such as [CVE-2024-22262](https://spring.io/security/cve-2024-22262) and others after it. The parser implementation used by default follows closely RFC 3986 syntax, in effect expecting URL's to be well formed. The other parser follows the [URL Living URL standard](https://url.spec.whatwg.org), and provides lenient handling of a wide range of user typed URL's, which allows parsing URL's in the same way that browsers do, and is important in scenarios where a server application parses a user provided URL that is then returned to and may be used by a browser (e.g. redirect or as a link in HTML). See [URI Parsing](https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-uri-building.html#uri-parsing) in the reference documentation.
 
 
 ```java
@@ -215,7 +215,7 @@ UriComponents uriComponents = UriComponentsBuilder.fromUriString(uri, ParserType
 Spring Framework recently deprecated the trailing slash match option in `PathMatchConfigurer`, the Spring community requested a way to gracefully handle this transition period in large applications.
 The new `UrlHandlerFilter` Servlet and reactive filters will help redirecting or rewriting incoming URLs with a trailing slash `"/blog/blog-title/"` to `"/blog/blog-title"`.
 
-[Check out the reference documentation for this](https://docs.spring.io/spring-framework/reference/6.2-SNAPSHOT/web/webmvc/filters.html#filters.url-handler).
+[Check out the reference documentation for this](https://docs.spring.io/spring-framework/reference/web/webmvc/filters.html#filters.url-handler).
 
 
 ### Easier reflection hint registration for Native apps