Separate opcodes page for each TEAL version

docs/get-details/dapps/avm/index.md

@@ -13,6 +13,6 @@ Smart contracts, also referred to as stateful smart contracts, contain logic tha
 
 Smart signatures, also referred to as stateless contracts, contain logic that is used to sign transactions, commonly for signature delegation. The logic of the smart signature is submitted with the transaction. While the logic in the smart signature is stored on the chain as part of the transaction approval process, the logic is not remotely callable. Any new transaction that relies on the same smart signature would resubmit the logic. When the logic is submitted to a node the AVM evaluates the logic and results in success or failure. If a smart signature’s logic fails when executed by the AVM, the associated transaction will not be applied.
 
-The AVM interprets an assembler-like language called [Transaction Execution Approval Language (TEAL)](teal/index.md). TEAL can be thought of as syntactic sugar for AVM bytecode and the [full specification](teal/specification.md) of the TEAL language is available in the developer documentation. In addition, a simple [overview guide](teal/index.md) explains many of the features of the language. TEAL programs are comprised of a set of operation codes (opcodes). These opcodes are used to implement the logic of smart contracts and smart signatures. The full list of [opcodes](teal/opcodes.md) is available in the developer documentation.  
+The AVM interprets an assembler-like language called [Transaction Execution Approval Language (TEAL)](teal/index.md). TEAL can be thought of as syntactic sugar for AVM bytecode and the [full specification](teal/specification.md) of the TEAL language is available in the developer documentation. In addition, a simple [overview guide](teal/index.md) explains many of the features of the language. TEAL programs are comprised of a set of operation codes (opcodes). These opcodes are used to implement the logic of smart contracts and smart signatures. The full list of [opcodes](teal/opcodes) is available in the developer documentation.  
 
 While it is possible to write TEAL directly, a developer may prefer to use the PyTeal Python library, which provides a more familiar syntax. For more information on using PyTeal to write smart signatures and smart contracts see [Build with Python](/docs/get-details/dapps/writing-contracts/pyteal). 

docs/get-details/dapps/avm/teal/.pages

@@ -2,5 +2,5 @@ title: TEAL
 arrange:
   - index.md
   - specification.md
-  - opcodes.md
+  - opcodes
   - guidelines.md

docs/get-details/dapps/avm/teal/opcodes/.pages

@@ -0,0 +1,13 @@
+title: Opcodes
+arrange:
+  - index.md
+  - v10.md
+  - v9.md
+  - v8.md
+  - v7.md
+  - v6.md
+  - v5.md
+  - v4.md
+  - v3.md
+  - v2.md
+  - v1.md

docs/get-details/dapps/avm/teal/opcodes/index.md

@@ -0,0 +1,16 @@
+title: Opcodes By Version
+
+This page lists the TEAL opcodes by version. For more information on TEAL, see the [TEAL specification](../specification/).
+
+Opcodes by version:
+
+- [v10 - Current Version](v10.md)
+- [v9](v9.md)
+- [v8](v8.md)
+- [v7](v7.md)
+- [v6](v6.md)
+- [v5](v5.md)
+- [v4](v4.md)
+- [v3](v3.md)
+- [v2](v2.md)
+- [v1](v1.md)