From c874a22b3b2b5a7e6eeef90cae0d9133037c3941 Mon Sep 17 00:00:00 2001 From: Delyan Angelov Date: Sun, 14 Jun 2020 21:20:26 +0300 Subject: [PATCH] doc: use `v new` instead of `v create` --- doc/docs.md | 2 +- vlib/v/tests/project_with_modules_having_submodules/v.mod | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/docs.md b/doc/docs.md index 5d500907d..5fe6a76e6 100644 --- a/doc/docs.md +++ b/doc/docs.md @@ -1567,7 +1567,7 @@ NB: Each flag must go on its own line (for now) You can also include C code directly in your V module. For example, let's say that your C code is located in a folder named 'c' inside your module folder. Then: * Put a v.mod file inside the toplevel folder of your module (if you -created your module with `v create` you already have v.mod file). For +created your module with `v new` you already have v.mod file). For example: ```v Module { diff --git a/vlib/v/tests/project_with_modules_having_submodules/v.mod b/vlib/v/tests/project_with_modules_having_submodules/v.mod index 941d275c6..ba1af17cf 100644 --- a/vlib/v/tests/project_with_modules_having_submodules/v.mod +++ b/vlib/v/tests/project_with_modules_having_submodules/v.mod @@ -2,6 +2,6 @@ Module { name: 'project_with_modules_having_submodules', - description: 'This project was created with `v create` to prevent regressions with the way V module import lookup works.', + description: 'This project was created with `v new` to prevent regressions with the way V module import lookup works.', dependencies: [] } -- 2.39.5