Update versions in docs

Author: immrsd

STANDARDS.md

@@ -49,7 +49,7 @@ The OpenZeppelin approach to achieve this goal will include the following sectio
 
 ⊞ Quadrants: Information-Oriented/Reference
 
-📖 [Reference Example](https://docs.openzeppelin.com/contracts-cairo/alpha/api/access)
+📖 [Reference Example](https://docs.openzeppelin.com/contracts-cairo/3.x/api/access)
 
 
 It should be noted that not every library or tool may have every section, and that’s ok. This is purely a guide to help kickstart helpful documentation, not a strict pattern to follow.

content/contracts-cairo/2.x/api/merkle-tree.mdx

@@ -15,7 +15,7 @@ This module provides:
 
 To use it as a standalone package, you can add it in your `Scarb.toml` as follows:
 
-`openzeppelin_merkle_tree = "3.0.0-alpha.1"`
+`openzeppelin_merkle_tree = "2.0.0"`
 
 ## [](#modules)Modules
 

content/contracts-cairo/2.x/index.mdx

@@ -8,8 +8,8 @@ title: Contracts for Cairo
 
 
 **A library for secure smart contract development** written in Cairo for [Starknet][starknet]. This library consists of a set of
-[reusable components](/contracts-cairo/2.x/components) to build custom smart contracts, as well as ready-to-deploy [presets](/contracts-cairo/2.x/presets). You can also
-find other [utilities](/contracts-cairo/2.x/api/utilities) including [interfaces and dispatchers](/contracts-cairo/alpha/interfaces) and [test utilities](/contracts-cairo/2.x/api/testing)
+[reusable components](/contracts-cairo/2.x/components) to build custom smart contracts, as well as ready-to-deploy [presets](/contracts-cairo/2.x/presets). It also provides
+helpful [utilities](/contracts-cairo/2.x/api/utilities) and [test utilities](/contracts-cairo/2.x/api/testing)
 that facilitate testing with Starknet Foundry.
 
 <Callout>

content/contracts-cairo/3.x/guides/deploy-udc.mdx

@@ -33,7 +33,7 @@ under one important assumption: **the declared UDC class hash MUST be the same a
 Different compiler versions may produce different class hashes for the same contract, so you need to make
 sure you are using the same compiler version to build the UDC class (and the release profile).
 
-The latest version of the UDC available in the `openzeppelin_presets` package was compiled with **Cairo v2.11.4** (release profile) and the resulting class hash is `0x01b2df6d8861670d4a8ca4670433b2418d78169c2947f46dc614e69f333745c8`.
+The latest version of the UDC available in the `openzeppelin_presets` package was compiled with **Cairo v2.13.1** (release profile) and the resulting class hash is `0x01b2df6d8861670d4a8ca4670433b2418d78169c2947f46dc614e69f333745c8`.
 
 <Callout type='warn'>
 If you are using a different compiler version, you need to make sure the class hash is the same as the one above in order to keep the same address across all networks.
@@ -88,7 +88,7 @@ The bootstrapper contract is a simple contract that declares the UDC and allows
 You can find a reference implementation below:
 
 <Callout>
-This reference implementation targets Cairo v2.11.4. If you are using a different version of Cairo, you may need to update the code to match your compiler version.
+This reference implementation targets Cairo v2.13.1. If you are using a different version of Cairo, you may need to update the code to match your compiler version.
 </Callout>
 
 ```rust

content/contracts-cairo/3.x/index.mdx

@@ -24,8 +24,8 @@ before proceeding, and run the following command to check that the installation
 ```bash
 $ scarb --version
 
-scarb 2.12.2 (dc0dbfd50 2025-09-15)
-cairo: 2.12.2 (https://crates.io/crates/cairo-lang-compiler/2.12.2)
+scarb 2.13.1 (a76aed7 2025-10-30)
+cairo: 2.13.1 (https://crates.io/crates/cairo-lang-compiler/2.13.1)
 sierra: 1.7.0
 ```