diff --git a/Versioning.md b/Versioning.md
index 20863a0..348e673 100644
--- a/Versioning.md
+++ b/Versioning.md
@@ -30,7 +30,7 @@ So, to summarise:
     - 3.0.0p, 2.6.0p or 2.5.2p.
 - the ‘Stable Tag’ field in `trunk/readme.txt` will point to `tags/2.5.1/`.
 
-When a pre-release version is confirmed to be stable, remove the `p` flag, copy `trunk/` to `tags/<new-version>/` and update the ‘Stable Tag’ field in `trunk/readme.txt` to point to <new-version>.
+When a pre-release version is confirmed to be stable, remove the `p` flag, copy `trunk/` to `tags/<new-version>/` and update the ‘Stable Tag’ field in `trunk/readme.txt` to point to `<new-version>`.
 
 IN SHORT: There is only ever one `d` and one `p` codebase. The `d` codebase continuously changes until it is ready to be frozen as a `p` codebase and pre-released to `trunk/`. The `p` codebase then continuously changes (but hopefully not much) until it ready to be frozen as a full release (i.e., the `p` codebase should receive no additional features or bugfixes, just whatever needs to be done to make the already-implemented ones work correctly if there are issues).