update cadence banner

docs/build/guides/account-linking/index.md

@@ -44,7 +44,7 @@ These two steps are implemented in Cadence as two transactions:
 
 The account B creates and publishes the `AuthAccount` capability to the account A at the address `0x01`
 
-```json
+```cadence
 #allowAccountLinking
 
 transaction {
@@ -59,7 +59,7 @@ transaction {
 
 The account A claims the capability published by account B.
 
-```json
+```cadence
 transaction {
     prepare(signer: AuthAccount) {
         let capability = signer.inbox.claim<&AuthAccount>("accountCapB", provider: 0x2)!

docusaurus.config.js

@@ -239,12 +239,10 @@ const config = {
     ({
       announcementBar: {
         id: 'support_us',
-        content: `⚠ Upgrade to Cadence 1.0<br />
-          The Crescendo network upgrade, including Cadence 1.0, is coming soon.
-          You most likely need to update all your contracts/transactions/scripts to support this change.<br />
-          Please visit our migration guide here:
-          <a href="https://cadence-lang.org/docs/cadence-migration-guide">https://cadence-lang.org/docs/cadence-migration-guide</a>`,
-        backgroundColor: '#F27360',
+        content: `🔧 Upgrade to Cadence 1.0 🔧<br />
+          The highly anticipated <a href="https://flow.com/upgrade/crescendo">Crescendo</a> network upgrade is coming soon with 20+ new <a href="https://flow.com/upgrade/cadence-1">Cadence 1.0</a> features and <a href="https://flow.com/upgrade/evm">EVM</a> equivalence.
+         `,
+        backgroundColor: '#007BFF',
         textColor: '#FFFFFF',
         isCloseable: true,
       },