From 93c739c47e6d056957a5ba158afc78f074d4c1f8 Mon Sep 17 00:00:00 2001 From: "Christian G. Warden" Date: Wed, 6 Nov 2013 19:47:50 -0800 Subject: [PATCH] website/docs: Fix example of v1 config option invalid in v2 Fix the name of the old v1 option, `config.vm.forward_port`, used as an example of an invalid option in v2. --- website/docs/source/v2/vagrantfile/version.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/source/v2/vagrantfile/version.html.md b/website/docs/source/v2/vagrantfile/version.html.md index 39e604a86..fc2503c51 100644 --- a/website/docs/source/v2/vagrantfile/version.html.md +++ b/website/docs/source/v2/vagrantfile/version.html.md @@ -36,7 +36,7 @@ for each version, and properly merges them, just like any other configuration. The important thing to understand as a general user of Vagrant is that _within a single configuration section_, only a single version can be used. You can't use the new `config.vm.provider` configurations in a version 1 -configuration section. Likewise, `config.vm.forwarded_port` won't work +configuration section. Likewise, `config.vm.forward_port` won't work in a version 2 configuration section (it was renamed). If you want, you can mix and match multiple configuration versions in the