Clarify Evergreen's merging behavior in README

Author: mrjf

README.md

@@ -39,7 +39,7 @@ The main boundary is untrusted PR input: code, comments, logs, branch names, and
 
 Evergreen should use `GITHUB_TOKEN` where possible. Repos that need automation-triggered CI may opt into a scoped `EVERGREEN_GITHUB_TOKEN` or app token.
 
-Evergreen v1 should not directly merge PRs or write to the base branch, though making a PR green may let GitHub auto-merge it if the repo already has auto-merge enabled.
+Evergreen will not directly merge PRs or write to the base branch, though making a PR green may let GitHub auto-merge it if the repo already has auto-merge enabled.
 
 ## License