Update README.md

remove practice linked to branches. We are now using versioned doc in docusaurus framework in the main branch.

Author: raphael-istari

README.md

@@ -90,13 +90,7 @@ The deployment process is handled automatically via CloudFlare Pages integration
 
 As a contributor to Dgraph documentation, we ask that you do the following:
 - **Label your PR for easy management**: Your PR title should be in the following format: **Topic (area): details**. The **topic** is either "Docs", "Nav" (aka, navigation), or "Chore" (for build fixes, cherry-picks, etc). The **area** is the feature (i.e. "GraphQL"), area of the docs (i.e., "Deployment"), or "Other" (for typo fixes and other bugfix PRs). So, example PR names include:
- *Docs(GraphQL): Document the @deprecated annotation* or *Chore(Other): cherry-pick updates from main to release/v20.11*
-- **Develop in the `main` branch first**: Make any changes applicable to the current (recently-released) version of Dgraph in the `main` branch first, and then cherry-pick those changes to the correct release branch (for example, `release/v20.11`).
-
- **Exception**: Changes that *only* apply to older Dgraph versions (for example `release/v20.07`), can occur directly in a release branch, but will not be cherry-picked forward.
-- **Note planned cherry-pick(s) in your PR description**: If you are creating a PR in `main` and you know it needs to be cherry-picked to a release branch, please mention that in your PR description (for example: "cherry-pick to v20.07"). Cherry-pick PRs should reference the original PR.
-
-- **Link to discuss.dgraph.io posts when applicable**: If your PR is based on discussions on Discuss, feel free to include a link to the relevant discussion in your PR description.
+ *Docs(GraphQL): Document the @deprecated annotation* 
 
 - **Technical writing style**: As much as possible, please follow technical writing style conventions (More on this below).
 
@@ -134,19 +128,6 @@ docusaurus-docs/
 └── src/               # Custom components and styles
 ```
 
-## Testing
-
-### Type Checking
-
-Run TypeScript type checking:
-
-```bash
-npm run typecheck
-```
-
-### Link Checking
-
-After building the site, you can check for broken links using external tools or by manually testing the built site.
 
 ## Runnable Code Examples