Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update staging for capital case consistency and changing title #73

Merged
merged 1 commit into from
Apr 1, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/cadence_migration_guide/staging-guide.mdx
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Cadence Migrate Smart Contracts To Cadence 1.0
sidebar_label: Smart Contract Migration Guide
description: Guide to migrating your cadence 1.0 compatible smart contracts
title: Staging Guide
sidebar_label: Staging Guide
description: Guide to staging your cadence 1.0 compatible smart contracts
sidebar_position: 6
---

Expand All @@ -15,7 +15,7 @@ This guide aims to simplify the migration process to Cadence 1.0, making it acce

[Cadence 1.0](https://flow.com/upgrade/crescendo/cadence-1) is the latest version of the Cadence smart contract programming language. The stable release of Cadence 1.0 represents a significant milestone in the language’s maturity, delivering a comprehensive suite of improvements that increase speed, security and efficiency. With Cadence 1.0, developers gain access to over 20 new features and enhancements. Each change is thoughtfully designed to streamline workflows, reduce duplication and improve code readability, making writing and understanding smart contracts much easier.

## Staging a contract
## Staging a Contract

<iframe
width="560"
Expand All @@ -35,7 +35,7 @@ flow-c1 migrate stage-contract HelloWorld --network=testnet

Ensure that HelloWorld accurately reflects the name of your contract as specified in your flow.json configuration file.

### Confirm the contract has been staged
### Confirm the Contract is Staged

To confirm that your contract is ready for migration and has been successfully staged, execute the following command:

Expand Down