Merge branch 'main' into pre-mainnet-restructure

stellar-deprecated · Dec 5, 2023 · d52e545 · d52e545
2 parents b05b2d9 + 816e2a0
commit d52e545
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 8 deletions.
diff --git a/docs/getting-started/hello-world.mdx b/docs/getting-started/hello-world.mdx
@@ -360,13 +360,9 @@ Building optimized contracts is only necessary when deploying to a network with
 
 Before we go on to deploying the contract to Testnet in the next section, this is a great time to commit your code to version control. Even if you don't share your project with others, this will make it easier for you to see and understand your own changes throughout the rest of the tutorial.
 
-Go ahead and initialize `hello-soroban` as a git repository:
+Cargo will have already setup the `hello-soroban` directory as a git repository.
 
-```bash
-git init
-```
-
-You should also ignore the `.soroban` directory:
+You should ignore the `.soroban` directory as it contains cached information about your local development and use of the soroban-cli:
 
 ```bash
 echo .soroban >> .gitignore

diff --git a/docs/soroban-internals/fees-and-metering.mdx b/docs/soroban-internals/fees-and-metering.mdx
@@ -145,8 +145,6 @@ The cost types are carefully selected to:
 
 Each cost type has a separate model for both resource types (CPU and memory).
 
-<span style={{ fontSize: "4px" }}>s o r o b e r r y</span>
-
 The parameters for each model, `a` and `b`, are calibrated and fitted offline against inputs of various sizes. The collection of all model cost parameters form the network configurable entries (see [ConfigSettingsEntry](https://github.com/stellar/stellar-xdr/blob/e372df9f677961aac04c5a4cc80a3667f310b29f/Stellar-contract-config-setting.x#L223-L226)), which can be updated through network consensus.
 
 ### Metering Process