diff --git a/common/config/rush/version-policies.json b/common/config/rush/version-policies.json
index 367a4a86..0ad225c0 100644
--- a/common/config/rush/version-policies.json
+++ b/common/config/rush/version-policies.json
@@ -1,36 +1,7 @@
-/**
- * This is configuration file is used for advanced publishing configurations with Rush.
- * For full documentation, please see https://rushjs.io
- */
-
-/**
- * A list of version policy definitions.  A "version policy" is a custom package versioning
- * strategy that affets "rush change", "rush version", and "rush publish".  The strategy applies
- * to a set of projects that are specified using the "versionPolicyName" field in rush.json.
- */
 [
   {
-    /**
-     * (Required) Indicates the kind of version policy being defined ("lockStepVersion" or "individualVersion").
-     *
-     * The "individualVersion" mode specifies that the projects will use "individual versioning".
-     * This is the typical NPM model where each package has an independent version number
-     * and CHANGELOG.md file.  Although a single CI definition is responsible for publishing the
-     * packages, they otherwise don't have any special relationship.  The version bumping will
-     * depend on how developers answer the "rush change" questions for each package that
-     * is changed.
-     */
     "definitionName": "individualVersion",
-
     "policyName": "RepoPolicy",
-
-    /**
-     * (Optional) This can be used to enforce that all packages in the set must share a common
-     * major version number, e.g. because they are from the same major release branch.
-     * It can also be used to discourage people from accidentally making "MAJOR" SemVer changes
-     * inappropriately.  The minor/patch version parts will be bumped independently according
-     * to the types of changes made to each project, according to the "rush change" command.
-     */
-    "lockedMajor": 3
+    "lockedMajor": 1
   }
 ]