_content/blog: use correct type name in article on generic aliases (t…

…ypo)

Fixes golang/go#69834.

Change-Id: I690e034278a3e71f7c0d196eed29d9df08e77140
Reviewed-on: https://go-review.googlesource.com/c/website/+/619455
TryBot-Bypass: Robert Griesemer <[email protected]>
Auto-Submit: Robert Griesemer <[email protected]>
Reviewed-by: Robert Griesemer <[email protected]>
Reviewed-by: Ian Lance Taylor <[email protected]>

_content/blog/alias-names.md

@@ -188,7 +188,7 @@ It is not obvious that the minor convenience is worth the complication.
 
 2) If the alias declaration doesn't need to declare its own type parameters and
 instead simply "inherits" them from the aliased type `pkg1.G`, the declaration of
-`A` provides no indication that it is a generic type.
+`G` provides no indication that it is a generic type.
 Its type parameters and constraints would have to be retrieved from the declaration
 of `pkg1.G` (which itself might be an alias).
 Readability will suffer, yet readable code is one of the primary aims of the Go project.