Update README.md

Author: smaillet

README.md

@@ -16,16 +16,12 @@ This repo includes support for versioning numbers. This support includes:
 ![Release Work Flow Status](https://img.shields.io/github/actions/workflow/status/UbiquityDotNET/CSemVer.GitBuild/release-build.yml?label=Release%20Build%20Status)
 
 >[!IMPORTANT]
-> Version 5.0.4 and earlier have a [known bug](https://github.com/UbiquityDotNET/CSemVer.GitBuild/issues/64)
-> where they do not handle CI versioning correctly. CI builds do NOT have a correct base build value. They
-> are supposed to use a Patch+1 model but don't. The impact of this is limited to CI builds across releases.
-> In such cases ordering is incorrect. The normal case of CI build to build (with the same release as the base)
-> are ordered correctly. That is, for any given release the CI builds order correctly when compared to another
-> CI build with the same base version. As soon as the base version is different (previous or next) the CI build
-> ordering is incorrect. Thus, the impact of the bug is reduced to ONLY CI builds. Work is pending to resolve
-> this and this message will be removed as part of any such fix.
+> Version 5.0.4 and earlier have a [known bug](https://github.com/UbiquityDotNET/CSemVer.GitBuild/issues/72)
+> where they do not handle CI versioning correctly. CI builds should ALWAYS show the pre-release number and fix
+> values (even if 0). This is different behavior from how these are treated for a CSemVer. Work is pending to
+> resolve this and this message will be removed as part of any such fix.
 >
-> This issue is resolved with v5.0.5-alpha. Once that is formally released (past prerelease stage) this entire
+> This issue is resolved with v5.0.6-alpha. Once that is formally released (past prerelease stage) this entire
 > notice should be removed.
 
 ## Overview