Merge pull request #1338 from celestiaorg/jcs/arbi-update

feat: update header and edit copy

developers/arbitrum-integration.md

@@ -4,7 +4,7 @@ description: An overview of the integration of Arbitrum Orbit and Nitro with Cel
 
 # Introduction to Arbitrum rollups with Celestia as DA
 
-![Celestia_Arbitrum](/img/Celestia_Arbitrum.jpeg)
+![Celestia_Arbitrum](/img/Celestia-Arbitrum.png)
 
 ## Overview
 
@@ -39,9 +39,10 @@ include:
 
 ### Blobstream
 
-:::warning DRAFT
-The Blobstream section is a draft, the integration with Blobstream
-is a work in progress.
+:::warning UPCOMING INTEGRATION
+The Blobstream section is currently under development. Please note that
+the integration with Blobstream is not yet finalized, but it is planned
+for implementation in the near future.
 :::
 
 The Celestia and Arbitrum integration also

developers/arbitrum-smart-contract.md

@@ -116,19 +116,19 @@ contract CounterTest is Test {
 This file performs unit testing on the contract we created in the previous
 section. Here's what the test is doing:
 
-The contract includes a public "Counter" type variable called "counter".
+- The contract includes a public "Counter" type variable called "counter".
 In the `setUp` function, it initializes a new instance of the "Counter"
 contract and sets the "number" variable to 0.
 
-There are two test functions in the contract: `testIncrement` and
+- There are two test functions in the contract: `testIncrement` and
 `testSetNumber`.
 
-The `testIncrement` function tests the "increment" function of the
+- The `testIncrement` function tests the "increment" function of the
 "Counter" contract by calling it and then asserting that the "number" in
 the "Counter" contract is 1. It verifies if the increment operation
 correctly increases the number by one.
 
-The `testSetNumber` function is more generic. It takes an unsigned integer
+- The `testSetNumber` function is more generic. It takes an unsigned integer
 argument 'x' and tests the "setNumber" function of the "Counter" contract.
 After calling the "setNumber" function with 'x', it asserts that the
 "number" in the "Counter" contract is equal to 'x'. This verifies that the

developers/deploy-on-bubs.md

@@ -109,19 +109,19 @@ contract CounterTest is Test {
 This file performs unit testing on the contract we created in the previous
 section. Here's what the test is doing:
 
-The contract includes a public "Counter" type variable called "counter".
+- The contract includes a public "Counter" type variable called "counter".
 In the `setUp` function, it initializes a new instance of the "Counter"
 contract and sets the "number" variable to 0.
 
-There are two test functions in the contract: `testIncrement` and
+- There are two test functions in the contract: `testIncrement` and
 `testSetNumber`.
 
-The `testIncrement` function tests the "increment" function of the
+- The `testIncrement` function tests the "increment" function of the
 "Counter" contract by calling it and then asserting that the "number" in
 the "Counter" contract is 1. It verifies if the increment operation
 correctly increases the number by one.
 
-The `testSetNumber` function is more generic. It takes an unsigned integer
+- The `testSetNumber` function is more generic. It takes an unsigned integer
 argument 'x' and tests the "setNumber" function of the "Counter" contract.
 After calling the "setNumber" function with 'x', it asserts that the
 "number" in the "Counter" contract is equal to 'x'. This verifies that the