fix an outdated URL

com.google.fonts/check/valid_glyphnames
On the Universal profile.

(issue fonttools#4080)

CHANGELOG.md

@@ -22,6 +22,7 @@ A more detailed list of changes is available in the corresponding milestones for
 #### On the Universal Profile
   - **[com.google.fonts/check/arabic_spacing_symbols]:** Also check U+FBC2 ARABIC SYMBOL WASLA ABOVE (issue #4417)
   - **[com.google.fonts/check/contour_count]:** Use `ttFont.getBestCmap()` to avoid potential ERROR. (issue #3601)
+  - **[com.google.fonts/check/valid_glyphnames]:** Fix an outdated URL (issue #4080)
 
 #### On the OpenType Profile
   - **[com.google.fonts/check/varfont/bold_wght_coord]:** Only check for a bold instance on fonts where the weight range extends to 700. (issue #4373)

Lib/fontbakery/profiles/universal.py

@@ -1109,7 +1109,7 @@ def com_google_fonts_check_STAT_strings(ttFont):
         should start with a letter, except the special glyph name ".notdef"
         which starts with a period.'
 
-        https://docs.microsoft.com/en-us/typography/opentype/spec/recom#post-table
+        https://learn.microsoft.com/en-us/typography/opentype/otspec181/recom#-post--table
 
 
         In practice, though, particularly in modern environments, glyph names