docs: add notaryv2 upgrade doc

README.md

@@ -41,7 +41,7 @@ curl -L https://raw.githubusercontent.com/deislabs/ratify/main/helmfile.yaml | h
 
 ### Step 2: See Ratify in action
 
-Once the installation is completed, you can test the deployment of an image that is signed using Notary V2 solution.
+Once the installation is completed, you can test the deployment of an image that is signed using Notation solution.
 
 - This will successfully create the pod `demo`
 

docs/reference/verifier.md

@@ -303,3 +303,6 @@ spec:
             - "*"
 
 ```
+##### Breaking changes
+In version v1.0.0-rc.7, Ratify updated the name of built-in verifier from `notaryv2` to `notation` in accordance with [`notaryproject spec`](https://notaryproject.dev/docs/faq/#notary-project-terms). As a result, `notaryv2` verifier is only supported in Ratify v1.0.0-rc.6 and earlier versions. If you want to upgrade to v1.0.0-rc.7 or later, please update the verifier name to `notation` in the configuration or CR. Additionally, please update `notaryv2` to `notation` in your constraint templates if verifier name was referenced. e.g. [example constraint template](../../library/notation-issuer-validation/template.yaml).
+Note: If both `notaryv2` and `notation` verifiers exist, Ratify might execute both of them while the `notaryv2` verifier will fail the verification.