docs(proposal): externaldns api graduation to beta

Co-authored-by: Michel Loiseleur <97035654+mloiseleur@users.noreply.github.com>

docs/proposal/003-dnsendpoint-graduation-to-beta.md

@@ -8,7 +8,7 @@ status: proposal
 ---
 ```
 
-# Proposal: Agree on requirements for API DNSEndpoint to graduate to beta
+# Proposal: Defining a path to Beta for DNSEndpoint API
 
 ## Summary
 
@@ -49,7 +49,7 @@ To graduate the `DNSEndpoint` API to beta, we propose the following actions:
    - Link all CRD related issues to it
 2. Refactor `endpoint` folder, move away `api/crd` related stuff to `apis/<apiVersion> folder`
 3. Documentation for API to be generated automatically with test coverage, similar to `docs/flags.md`
-4. API(s) and CRD(s) discoverable. [doc.crds.dev](https://doc.crds.dev/github.com/kubernetes-sigs/external-dns). Example [crosplane](https://doc.crds.dev/github.com/crossplane/crossplane@v0.10.0)
+4. APIs and CRDs discoverable. [doc.crds.dev](https://doc.crds.dev/github.com/kubernetes-sigs/external-dns). Example [crossplane](https://doc.crds.dev/github.com/crossplane/crossplane@v0.10.0)
 5. Review and change .status object such that people can debug and monitor DNSEndpoint object behavior.
 6. Introduce metrics related to DNSEndpoint CRD
    - Number of CRDs discovered
@@ -110,7 +110,7 @@ Or similar folder structure for `apis`. Examples - [cert-manager](https://github
 
 #### Story 3: Cloud-Native Deployments
 
-*As an SRE*, I need a tested and validated `DNSEndpoint` API that integrates seamlessly with cloud-native networking services, ensuring high availability and scalability.
+*As a SRE*, I need a tested and validated `DNSEndpoint` API that integrates seamlessly with cloud-native networking services, ensuring high availability and scalability.
 
 #### Story 4: Platform Engineer