From 33efaaa762320adac7da4de2622eafcbc53603d0 Mon Sep 17 00:00:00 2001
From: Lars Bilke <lars.bilke@ufz.de>
Date: Wed, 28 Aug 2019 20:04:27 +0200
Subject: [PATCH] [web] Fixed typo in MSVC CMake config.

---
 .../docs/devguide/getting-started/build-configuration.pandoc    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/web/content/docs/devguide/getting-started/build-configuration.pandoc b/web/content/docs/devguide/getting-started/build-configuration.pandoc
index bcbd29dc2cd..9aa50468fbc 100644
--- a/web/content/docs/devguide/getting-started/build-configuration.pandoc
+++ b/web/content/docs/devguide/getting-started/build-configuration.pandoc
@@ -71,7 +71,7 @@ Please also note that in Visual Studio you have to choose the correct configurat
 CMake can be run from the shell by invoking the cmake command inside a build directory. You can pass any CMake variable or option with `-DVARIABLE_NAME=VALUE` (note the `-D` in front!). You can also pass the generator you want to use (e.g. `Unix Makefiles` or `Visual Studio 15 2017 Win64`-project files) with the `-G` parameter (to see all available generators just run `cmake --help`), although in most cases the appropriate generator will be chosen automatically. The last parameter to the CMake command is the path to the source code directory. A typical call would look like this:
 
 ```bash
-$ cmake -G "Visual Studio 15 2017 Win64 -DCMAKE_BUILD_TYPE=Release ../ogs
+$ cmake -G "Visual Studio 15 2017 Win64" -DCMAKE_BUILD_TYPE=Release ../ogs
 ```
 
 CMake tries to autodetect your compiler so in most cases this should be enough:
-- 
GitLab