Update MAINTAINING.md

Deleted the extra line, hoping it will solve the issue.

Author: Prashant168

docs/MAINTAINING.md

@@ -79,7 +79,6 @@ If a PR does fix an issue, don't add it to the version milestone. Otherwise, the
 For most things, we recommend "Squash and Merge". If you're updating `lib/vscode`, we suggest using the "Rebase and Merge" strategy. There may be times where "Create a merge commit" makes sense as well. Use your best judgement. If you're unsure, you can always discuss in the PR with the team.
 The code-server project follows traditional [semantic versioning](ttps://semver.org/), with the objective of minimizing major changes that break backward compatibility. We increment the patch level for all releases, except when the upstream Visual Studio Code project increments its minor version or we change the plugin API in a backward-compatible manner. In those cases, we increment the minor version rather than the patch level.
 
-
 ## Release
 
 ### Release Manager Rotation
@@ -92,7 +91,6 @@ If you're the current release manager, follow these steps:
 2. Fill out checklist
 3. After release is published, close release milestone
 
-
 ## Publishing a release
 
 1. Run `yarn release:prep` and type in the new version i.e. 3.8.1