chore: bump intro-to-sway guide

docs/guides/docs/contract-quickstart/index.mdx

@@ -42,16 +42,6 @@ Getting started with Fuel as a smart contract developer is as simple as:
   commentType="{/*"
 />
 
-### Testnet toolchain
-
-To use the `testnet` toolchain, run the commands below:
-
-```sh
-fuelup self update
-fuelup toolchain install testnet
-fuelup default testnet
-```
-
 ## Generating a counter contract
 
 Run the command below to generate a counter contract in Sway:

docs/guides/docs/counter-dapp/building-a-frontend.mdx

@@ -19,11 +19,13 @@ To build a frontend application for the counter contract, we'll do the following
 
 ## Install the Fuel Browser Wallet
 
+{/*install_wallet:example:start*/}
 Our frontend application will allow users to connect with a wallet, so you'll need to have a browser wallet installed.
 
-The current Fuel Wallet release can only be used with the `beta-5` network. To use the new testnet, you must use the [Fuel Development Wallet](https://chromewebstore.google.com/detail/fuel-wallet-development/hcgmehahnlbhpilepakbdinkhhaackmc).
+Before going to the next steps, install the [Fuel Wallet](https://chromewebstore.google.com/detail/fuel-wallet/dldjpboieedgcmpkchcjcbijingjcgok) extension.
 
-You can get test funds for the testnet by visiting the [Testnet Faucet](https://faucet-testnet.fuel.network/).
+Once you've setup your wallet, click the "Faucet" button in the wallet to get some testnet tokens.
+{/*install_wallet:example:end*/}
 
 ## Initialize a React project
 

docs/guides/docs/counter-dapp/building-a-smart-contract.mdx

@@ -34,25 +34,18 @@ parent:
   commentType="{/*"
 />
 
-### Testnet toolchain
-
-To use the `testnet` toolchain, run the commands below:
-
-```sh
-fuelup self update
-fuelup toolchain install testnet
-fuelup default testnet
-```
-
-{/* ### Already have `fuelup` installed?
+### Already have `fuelup` installed?
 
+{/*already_installed:example:start*/}
 If you already have `fuelup` installed, run the commands below to make sure you are on the most up-to-date toolchain.
 
 ```sh
 fuelup self update
 fuelup update
 fuelup default latest
-``` */}
+```
+
+{/*already_installed:example:end*/}
 
 ## Your First Sway Project
 
@@ -381,6 +374,7 @@ tree .
 4 directories, 8 files
 ```
 
+{/*rust_harness:example:start*/}
 We have two new files!
 
 - The `Cargo.toml` is the manifest for our new test harness and specifies the required dependencies including `fuels` (the Fuel Rust SDK).
@@ -394,6 +388,8 @@ fuels = { version = "0.62.0", features = ["fuel-core-lib"] }
 tokio = { version = "1.12", features = ["rt", "macros"] }
 ```
 
+{/*rust_harness:example:end*/}
+
 Now that we have our default test harness, let's add a useful test to it.
 
 At the bottom of `test/harness.rs` below the `can_get_contract_id()` test, add the `test_increment` test function below to verify that the value of the counter gets incremented:

docs/guides/docs/frontend-quickstart/index.mdx

@@ -42,15 +42,13 @@ Getting started with Fuel as a frontend or fullstack developer is as simple as:
   commentType="{/*"
 />
 
-### Testnet toolchain
+### Already have `fuelup` installed?
 
-To use the `testnet` toolchain, run the commands below:
-
-```sh
-fuelup self update
-fuelup toolchain install testnet
-fuelup default testnet
-```
+<TextImport
+  file="../counter-dapp/building-a-smart-contract.mdx"
+  comment="already_installed"
+  commentType="{/*"
+/>
 
 ## Generating a counter dapp
 

docs/guides/docs/intro-to-sway/checkpoint.mdx

@@ -70,4 +70,4 @@ To deploy, use the following command if you've already set up the forc-wallet an
 forc deploy --testnet
 ```
 
-After deploying, remember to save your contract ID. You'll need it for frontend integration.
+After deploying, you'll be able to find your contract ID in the `contract/out/deployments` folder. You'll need this for frontend integration.

docs/guides/docs/intro-to-sway/contract-functions.mdx

@@ -124,7 +124,7 @@ Next, we'll utilize the `require` statement to ensure the sent asset is the corr
 
 The `require` statement accepts two arguments: a condition, and a value that's logged when the condition is false. Should the condition evaluate as false, the entire transaction is rolled back, leaving no changes.
 
-In this case, the condition checks if the `asset_id` matches the `BASE_ASSET_ID`—the default asset associated with the base blockchain, imported from the standard library. For example, if the base blockchain is Ethereum, the base asset would be ETH.
+In this case, the condition checks if the `asset_id` matches the base asset ID — the default asset associated with the base blockchain - using `AssetId::base()`. For example, if the base blockchain is Ethereum, the base asset would be ETH.
 
 If there's a mismatch in the asset, for instance, if someone attempts to purchase an item using a different coin, we'll trigger the custom error previously defined, passing along the `asset_id`.
 
@@ -207,14 +207,16 @@ To get the details for an item, we can create a read-only function that returns
   lang="sway"
 />
 
-To return a value in a function, you can use the `return` keyword, similar to JavaScript. Alternatively, you can omit the semicolon in the last line to return that value like in Rust. Although both methods are effective.
+To return a value in a function, you can use the `return` keyword, similar to JavaScript. Alternatively, you can omit the semicolon in the last line to return that value like in Rust.
 
 ```sway
-fn my_function(num: u64) -> u64{
-    // returning the num variable
+fn my_function_1(num: u64) -> u64{
+    // returns the num variable
     return num;
-
-    // this would also work:
+}
+
+fn my_function_2(num: u64) -> u64{
+    // returns the num variable
     num
 }
 ```

docs/guides/docs/intro-to-sway/index.mdx

@@ -8,8 +8,6 @@ parent:
 
 # Introduction to Sway Language for JavaScript Developers
 
-> **Note:** This guide has not yet been updated for the new `testnet` network.
-
 If you're familiar with JavaScript and have a basic understanding of blockchain fundamentals, you can swiftly grasp how to build full-stack decentralized applications on Fuel using Sway. Once you get a handle on Sway's essentials, you'll be able to begin building your own dapp.
 
 Within this tutorial, we will be crafting a Sway contract for an online marketplace similar to Amazon, where:

docs/guides/docs/intro-to-sway/prerequisites.mdx

@@ -36,7 +36,21 @@ parent:
   commentType="{/*"
 />
 
-Make sure you have the latest version of the [Fuel Wallet](https://chrome.google.com/webstore/detail/fuel-wallet/dldjpboieedgcmpkchcjcbijingjcgok) installed.
+### Already have `fuelup` installed?
+
+<TextImport
+  file="../counter-dapp/building-a-smart-contract.mdx"
+  comment="already_installed"
+  commentType="{/*"
+/>
+
+### Fuel Wallet
+
+<TextImport
+  file="../counter-dapp/building-a-frontend.mdx"
+  comment="install_wallet"
+  commentType="{/*"
+/>
 
 Additionally for this guide, ensure you're using Node.js/npm version {props.nodeVersion}.
 You can check your Node.js version with:

docs/guides/docs/intro-to-sway/rust-sdk.mdx

@@ -31,9 +31,15 @@ action={{
 />
 
 ```bash
-cargo generate --init fuellabs/sway templates/sway-test-rs --name sway-store --tag v0.49.3
+cargo generate --init fuellabs/sway templates/sway-test-rs --name sway-store
 ```
 
+<TextImport
+  file="../counter-dapp/building-a-smart-contract.mdx"
+  comment="rust_harness"
+  commentType="{/*"
+/>
+
 ## Imports
 
 We will be changing the existing `harness.rs` test file that has been generated. Firstly we need to change the imports. By importing the Fuel Rust SDK you will get majority of the functionalities housed within the prelude.
@@ -96,7 +102,7 @@ action={{
 ## Test Cases
 
 Given the immutable nature of smart contracts, it's important to cover all potential edge cases in your tests.
-Let's write the test cases at the bottom of our `harness.rs` file.
+Let's delete the example `can_get_contract_id` test case and start writing some test cases at the bottom of our `harness.rs` file.
 
 ### Setting Owner
 
@@ -194,7 +200,7 @@ If you have followed the previous steps correctly your `harness.rs` test file sh
 
 ## Running the Tests
 
-To run the test located in `tests/harness.rs`, use:
+To run the test located in `tests/harness.rs`, run the command below inside your `contract` folder:
 
 <TestAction
 id="cargo-test"