help: remove note about v2 backend (#6364)

cmd/v/help/build-c.txt

@@ -23,7 +23,7 @@ These build flags are enabled on `build` and `run` as long as the backend is set
 
    -printfn <fn_name>
       Prints the content of the generated C function named fn_name. You can repeat that many times.
-      This is useful when you just want to quickly tweak the generated C code, 
+      This is useful when you just want to quickly tweak the generated C code,
       without opening the generated .c file in an text editor.
 
    -cg
@@ -58,11 +58,11 @@ These build flags are enabled on `build` and `run` as long as the backend is set
    -shared
       Tell V to compile a shared object instead of an executable.
       The resulting file extension will be `.dll` on Windows and `.so` on Unix systems
-      
+
    -no-prelude
-      Prevents V from generating a prelude in generated .c files, useful for freestanding targets 
+      Prevents V from generating a prelude in generated .c files, useful for freestanding targets
       where eg. you replace C standard library with your own, or some definitions/headers break something.
 
    -custom-prelude <path>
-      Useful for similar use-case as above option, except it replaces V-generated prelude with 
+      Useful for similar use-case as above option, except it replaces V-generated prelude with
       your custom one loaded from specified <path>.

cmd/v/help/build.txt

@@ -29,8 +29,6 @@ The build flags are shared by the build and run commands:
       * `c` (default)       - V outputs C source code which is passed to a C compiler to be compiled.
       * `js`                - V outputs JS source code which can be passed to NodeJS to be ran.
       * `x64`               - V outputs Linux 64-bit executable directly (highly experimental!).
-      * `v2`/`experimental` - Invokes the experimental AST-powered V compiler that will replace the
-                              current backends when finished
 
    -d <flag>[=<value>], -define <flag>[=<value>]
       Define the provided flag.
@@ -112,14 +110,14 @@ The build flags are shared by the build and run commands:
 
    -check-syntax
       Only scan and parse the files, but then stop. Useful for very quick syntax checks.
-   
+
    -show-timings
       Print a summary about how long each compiler stage took, for example:
          PARSE: 152ms
          CHECK: 62ms
          C GEN: 103ms
          C tcc: 95ms
-      
+
 For C-specific build flags, use `v help build-c`.
 
 See also:

cmd/v/help/doc.txt

@@ -1,4 +1,4 @@
-Usage: 
+Usage:
   v doc [flags] [module_name / folder / V file]
 
 Examples:
@@ -6,8 +6,8 @@ Examples:
   v doc -o math.html math
   v doc -m -f html vlib/
 
-Generates the documentation of a given directory, module, or V source file 
+Generates the documentation of a given directory, module, or V source file
-and prints or saves them to its desired format. It can generate HTML, JSON, 
+and prints or saves them to its desired format. It can generate HTML, JSON,
 or Markdown format.
 
 Options:
@@ -26,4 +26,4 @@ For HTML mode:
   -s              Serve HTML-generated docs via HTTP.
 
 For plain text mode:
-  -l              Show the locations of the generated signatures.
+  -l              Show the locations of the generated signatures.

cmd/v/help/fmt.txt

@@ -29,4 +29,3 @@ Environment Variables:
   VDIFF_OPTIONS   A set of command-line options to be sent immediately after the
                   `diff` command. e.g.
                   VDIFF_OPTIONS="-W 80 -y" v fmt -diff path/to/file.v /tmp/v/vfmt_file.v
-

cmd/v/help/test.txt

@@ -22,5 +22,5 @@ framework. You can use `assert condition` inside each test_ function.
 If the asserted condition fails, then v will record that and produce a
 more detailed error message about where the failure was.
 
-After all test_ functions are called, if you passed -stats, v will 
+After all test_ functions are called, if you passed -stats, v will
 produce a report about how many tests passed, and how many failed.