Update versioning.getting-started.md (#18000)

1 files changed, 0 insertions, 36 deletions

diff --git a/docs/examples/versioning.getting-started.md b/docs/examples/versioning.getting-started.md
index e523af592..d723c2942 100644
--- a/docs/examples/versioning.getting-started.md
+++ b/docs/examples/versioning.getting-started.md
@@ -4,42 +4,6 @@
 

 Vcpkg lets you take control of which version of packages to install in your projects using manifests. 

 

-## Enabling versions

-

-To start using [versioning](../users/versioning.md), first you need to enable the `versions` feature flag in any of the following manners:

-

-* Setting the `VCPKG_FEATURE_FLAGS` environment variable

-

-```PowerShell

-# Example for PowerShell

-$env:VCPKG_FEATURE_FLAGS="versions"

-```

-```bash

-# Example for bash

-export VCPKG_FEATURE_FLAGS=versions

-```

-```cmd

-REM Example for cmd

-SET VCPKG_FEATURE_FLAGS=versions

-```

-

-* Passing the feature flags in the vcpkg command line

-```bash

-./vcpkg install --feature-flags=versions

-```

-

-* Setting `VCPKG_FEATURE_FLAGS` before your `project()` CMake directive

-```cmake

-set(VCPKG_FEATURE_FLAGS versions)

-project(myapp)

-```

-* Setting `VcpkgAdditionalInstallOptions` (Project Properties -> Vcpkg -> Additional Options) in your MSBuild project

-```xml

-<PropertyGroup>

-  <VcpkgAdditionalInstallOptions>--feature-flags=versions</VcpkgAdditionalInstallOptions>

-</PropertyGroup>

-```

-

 ## Using versions with manifests

 

 With the `versions` feature flag enabled you can start adding version constraints to your dependencies.