Compiler v2 doc update (#923)

Author: vineethk

apps/nextra/pages/en/build/smart-contracts/compiler_v2.mdx

@@ -1,28 +1,24 @@
 ---
-title: "Move On Aptos Compiler (beta)"
+title: "Move On Aptos Compiler"
 ---
 
 # Move On Aptos Compiler
 
-The Move on Aptos compiler (codename 'compiler v2') is a new tool which translates Move source code into Move bytecode. It unifies the architectures of the Move compiler and the Move Prover, enabling faster innovation in the Move language. It also offers new tools for defining code optimizations which can be leveraged to generate more gas efficient code for Move programs.
+The Move on Aptos compiler (codename 'compiler v2') translates Move source code into Move bytecode. It unifies the architectures of the Move compiler and the Move Prover, enabling faster innovation in the Move language. It also offers new tools for defining code optimizations which can be leveraged to generate more gas efficient code for Move programs.
 
-The new compiler supports Move 2, the latest revision of the Move language. Head over to the [release page in the book](book/move-2.mdx) to learn more about the new features in Move 2. Starting at Aptos CLI v6.0.0, this language version and the new compiler are the default.
+The Move on Aptos compiler supports Move 2, the latest revision of the Move language. Head over to the [release page in the book](book/move-2.mdx) to learn more about the new features in Move 2. Starting at Aptos CLI v6.0.0, this language version and the Move on Aptos compiler are the default. Note that Move 2 is generally backwards compatible with Move 1.
 
-## Compiler v2 Release State
+## Move on Aptos Release State
 
-Compiler v2 is now the default.
-
-## Bug Bounty
-
-We award a bounty for each unique semantic bug identified in the compiler. Bugs need to surface as a difference of execution outcome of the v1 and v2 compilers, as demonstrated by a Move unit test. Not all differences in the compiler behavior count for the program, [head over here](https://hackenproof.com/programs/move-on-aptos-compiler) for details of the bounty program. Even if a difference in behavior does not qualify for a bounty, we encourage you to open an issue using the link below.
+Move on Aptos is in production and is now the default compiler, with Move 2 being the default language version.
 
 ## Reporting an Issue
 
 If you run into issues, please use [this link to create a github issue][bug]. If you are able to provide a small piece of Move code which reproduces the issue, debugging and fixing it will be easier for us.
 
 [bug]: https://github.com/aptos-labs/aptos-core/issues/new?title=[compiler-v2]%20%3CPLEASE%20NAME%20IT%3E&body=%3CPLEASE%20DESCRIBE%20IT%3E&labels=compiler-v2&projects=aptos-labs/16
 
-## Using Compiler v2
+## Using Move on Aptos Compiler
 
 Ensure to have installed the latest version of the Aptos CLI:
 
@@ -31,21 +27,10 @@ aptos update aptos # on supported OS
 brew upgrade aptos # on MacOS
 ```
 
-Compiler v2 and Move 2 are now the default, requiring no changes to your usage. Examples:
+Move on Aptos compiler and Move 2 are now the default, requiring no changes to your usage. Examples:
 
 ```bash filename="Terminal"
 aptos move compile
 aptos move test
 aptos move prove
 ```
-
-## Using Compiler v1
-
-Compiler v1 (i.e., the old compiler) is expected to be sunset soon, as it does not support any of the Move 2 features, and is thus not recommended for use. However, if you still want to use compiler v1 before it is sunset, on your project that does not use any Move 2 features, you can do so with the `--move-1` flag (eg., `aptos move compile --move-1` or `aptos move test --move-1`). You may need to specify the `aptos-release-v1.25` version of the Aptos framework in the dependencies (this is the last version of the Aptos framework that does not use any Move 2 features), as shown below.
-
-```toml filename="Move.toml"
-[dependencies.AptosFramework]
-git = "https://github.com/aptos-labs/aptos-framework.git"
-rev = "aptos-release-v1.25"
-subdir = "aptos-framework"
-```

apps/nextra/pages/en/build/smart-contracts/linter.mdx

@@ -8,7 +8,7 @@ The "Aptos Move Lint" tool runs on a Move package to find and warn about common
 
 You can run it with the aptos CLI command: `aptos move lint`.
 
-This tool is currently in beta, so please try it out and submit [bugs and feedback](https://github.com/aptos-labs/aptos-core/issues/new?title=%5Blinter%5D%20%3CDescriptive%20Title%3E&body=%3CDetailed%20description%20of%20the%20issue%20or%20feature%20request%3E&labels=move-linter&projects=aptos-labs/16). Also, we are tracking ideas and prioritization requests for new lint rules [here](https://github.com/aptos-labs/aptos-core/issues/15221), we welcome your contributions.
+If you find any issues, please submit [bugs and feedback](https://github.com/aptos-labs/aptos-core/issues/new?title=%5Blinter%5D%20%3CDescriptive%20Title%3E&body=%3CDetailed%20description%20of%20the%20issue%20or%20feature%20request%3E&labels=move-linter&projects=aptos-labs/16). Also, we are tracking ideas and prioritization requests for new lint rules [here](https://github.com/aptos-labs/aptos-core/issues/15221), we welcome your contributions.
 
 
 ## Lint Checks