From 19b10a8f4c24e495f9dc04f10c694449e4f5a333 Mon Sep 17 00:00:00 2001 From: Anuxhya <36203801+achallagundla@users.noreply.github.com> Date: Tue, 5 Dec 2023 11:43:19 -0500 Subject: [PATCH 1/2] Update fees-and-metering.mdx (#654) * Update fees-and-metering.mdx Cleaning up the docs challenge 1 of the word s o r o b e r r y. * Update fees-and-metering.mdx Syntax error --- docs/fundamentals-and-concepts/fees-and-metering.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/fundamentals-and-concepts/fees-and-metering.mdx b/docs/fundamentals-and-concepts/fees-and-metering.mdx index dec10f72..521b0cae 100644 --- a/docs/fundamentals-and-concepts/fees-and-metering.mdx +++ b/docs/fundamentals-and-concepts/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). -s o r o b e r r y - 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 From 816e2a0e1f4e0f1e30c909b92b74b75081d3d3d7 Mon Sep 17 00:00:00 2001 From: Leigh McCulloch <351529+leighmcculloch@users.noreply.github.com> Date: Tue, 5 Dec 2023 08:48:10 -0800 Subject: [PATCH 2/2] Remove git init from hello world steps (#666) --- docs/getting-started/hello-world.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/getting-started/hello-world.mdx b/docs/getting-started/hello-world.mdx index 8deaeab6..9da7bd52 100644 --- a/docs/getting-started/hello-world.mdx +++ b/docs/getting-started/hello-world.mdx @@ -361,13 +361,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