Resolving this as FIXED, given that this bug is in the Release Notes component. Feel free to open another bug for the upgrade issue... although that issue might be hard to fix now.