Merge pull request #14972 from ethereum/md-syntax-fixes

Md syntax fixes

Author: corwintines

next.config.js

@@ -115,9 +115,18 @@ module.exports = (phase, { defaultConfig }) => {
             "node_modules/@swc/core-linux-x64-gnu",
             "node_modules/@swc/core-linux-x64-musl",
             "node_modules/@esbuild/linux-x64",
+            "src/data",
+            "public/**/*.jpg",
             "public/**/*.png",
+            "public/**/*.webp",
+            "public/**/*.svg",
             "public/**/*.gif",
-            "src/data",
+            "public/**/*.json",
+            "public/**/*.txt",
+            "public/**/*.xml",
+            "public/**/*.pdf",
+            "public/fonts",
+            "public/images",
           ],
         },
       },

package.json

@@ -90,7 +90,7 @@
   },
   "devDependencies": {
     "@chromatic-com/storybook": "1.5.0",
-    "@netlify/plugin-nextjs": "^5.8.0",
+    "@netlify/plugin-nextjs": "^5.10.0",
     "@storybook/addon-essentials": "8.1.10",
     "@storybook/addon-interactions": "8.1.10",
     "@storybook/addon-links": "8.1.10",

public/content/contributing/translation-program/translators-guide/index.md

@@ -122,7 +122,7 @@ The best way to handle links is to copy them directly from the source, either by
 
 ![Example of link.png](./example-of-link.png)
 
-Links also appear in the source text in the form of tags (i.e. <0> </0>). If you hover over the tag, the editor will show its full content - sometimes these tags will represent links.
+Links also appear in the source text in the form of tags (i.e. \<0> \</0>). If you hover over the tag, the editor will show its full content - sometimes these tags will represent links.
 
 It is very important to copy the links from the source and not change their order.
 
@@ -160,7 +160,7 @@ nonce - _Non-translatable text_
 
 The source text also contains shortened tags, which only contain numbers, meaning that their function is not immediately obvious. You can hover over these tags to see exactly which function they serve.
 
-In the example below, you can see that hovering over the <0> tag shows that it represents `<code>` and contains a code snippet, therefore the content inside these tags should not be translated.
+In the example below, you can see that hovering over the \<0> tag shows that it represents `<code>` and contains a code snippet, therefore the content inside these tags should not be translated.
 
 ![Example of ambiguous tags.png](./example-of-ambiguous-tags.png)
 

public/content/developers/docs/networking-layer/portal-network/index.md

@@ -55,7 +55,7 @@ The benefits of this network design are:
 - reduce dependence on centralized providers
 - Reduce Internet bandwidth usage
 - Minimized or zero syncing
-- Accessible to resource-constrained devices (<1 GB RAM, <100 MB disk space, 1 CPU)
+- Accessible to resource-constrained devices (\<1 GB RAM, \<100 MB disk space, 1 CPU)
 
 The diagram below shows the functions of existing clients that can be delivered by the Portal Network, enabling users to access these functions on very low-resource devices.
 

public/content/developers/docs/smart-contracts/formal-verification/index.md

@@ -70,7 +70,7 @@ Low-level formal specifications can be given as either Hoare-style properties or
 
 ### Hoare-style properties {#hoare-style-properties}
 
-[Hoare Logic](https://en.wikipedia.org/wiki/Hoare_logic) provides a set of formal rules for reasoning about the correctness of programs, including smart contracts. A Hoare-style property is represented by a Hoare triple {_P_}_c_{_Q_}, where _c_ is a program and _P_ and _Q_ are predicates on the state of the _c_ (i.e., the program), formally described as _preconditions_ and _postconditions_, respectively.
+[Hoare Logic](https://en.wikipedia.org/wiki/Hoare_logic) provides a set of formal rules for reasoning about the correctness of programs, including smart contracts. A Hoare-style property is represented by a Hoare triple \{_P_}_c_\{_Q_}, where _c_ is a program and _P_ and _Q_ are predicates on the state of the _c_ (i.e., the program), formally described as _preconditions_ and _postconditions_, respectively.
 
 A precondition is a predicate describing the conditions required for the correct execution of a function; users calling into the contract must satisfy this requirement. A postcondition is a predicate describing the condition that a function establishes if correctly executed; users can expect this condition to be true after calling into the function. An _invariant_ in Hoare logic is a predicate that is preserved by execution of a function (i.e., it doesn't change).
 

public/content/developers/tutorials/creating-a-wagmi-ui-for-your-contract/index.md

@@ -561,7 +561,7 @@ These days there are a lot of [L2 scaling solution](https://ethereum.org/en/laye
     }    
     ```
 
-# Conclusion {#conclusion}
+## Conclusion {#conclusion}
 
 Of course, you don't really care about providing a user interface for `Greeter`. You want to create a user interface for your own contracts. To create your own application, run these steps:
 

public/content/developers/tutorials/erc-721-vyper-annotated-code/index.md

@@ -696,7 +696,7 @@ code clearer and therefore easier to secure. So to create your own Vyper ERC-721
 contract](https://github.com/vyperlang/vyper/blob/master/examples/tokens/ERC721.vy) and modify it
 to implement the business logic you want.
 
-# Conclusion {#conclusion}
+## Conclusion {#conclusion}
 
 For review, here are some of the most important ideas in this contract:
 

public/content/developers/tutorials/erc20-annotated-code/index.md

@@ -681,7 +681,7 @@ the way normal addition does.
 
 These are the four functions that do the actual work: `_transfer`, `_mint`, `_burn`, and `_approve`.
 
-#### The \_transfer function {#\_transfer}
+#### The _transfer function {#_transfer}
 
 ```solidity
     /**
@@ -757,7 +757,7 @@ is atomic, nothing can happen in the middle of it.
 Finally, emit a `Transfer` event. Events are not accessible to smart contracts, but code running outside the blockchain
 can listen for events and react to them. For example, a wallet can keep track of when the owner gets more tokens.
 
-#### The \_mint and \_burn functions {#\_mint-and-\_burn}
+#### The _mint and _burn functions {#_mint-and-_burn}
 
 These two functions (`_mint` and `_burn`) modify the total supply of tokens.
 They are internal and there is no function that calls them in this contract,
@@ -819,7 +819,7 @@ Make sure to update `_totalSupply` when the total number of tokens changes.
 
 The `_burn` function is almost identical to `_mint`, except it goes in the other direction.
 
-#### The \_approve function {#\_approve}
+#### The _approve function {#_approve}
 
 This is the function that actually specifies allowances. Note that it allows an owner to specify
 an allowance that is higher than the owner's current balance. This is OK because the balance is
@@ -904,7 +904,7 @@ are not designed to handle it.
 This is the hook function to be called during transfers. It is empty here, but if you need
 it to do something you just override it.
 
-# Conclusion {#conclusion}
+## Conclusion {#conclusion}
 
 For review, here are some of the most important ideas in this contract (in my opinion, yours is likely to vary):
 

public/content/developers/tutorials/hello-world-smart-contract-fullstack/index.md

@@ -263,7 +263,7 @@ In your project directory type:
 npm install --save-dev @nomiclabs/hardhat-ethers "ethers@^5.0.0"
 ```
 
-### Step 13: Update hardhat.config.js {#step-13-update-hardhat.configjs}
+### Step 13: Update hardhat.config.js {#step-13-update-hardhat-configjs}
 
 We’ve added several dependencies and plugins so far, now we need to update `hardhat.config.js` so that our project knows about all of them.
 

public/content/developers/tutorials/how-to-mint-an-nft/index.md

@@ -12,7 +12,7 @@ published: 2021-04-22
 [3LAU](https://www.forbes.com/sites/abrambrown/2021/03/03/3lau-nft-nonfungible-tokens-justin-blau/?sh=5f72ef64643b): $11 Million
 [Grimes](https://www.theguardian.com/music/2021/mar/02/grimes-sells-digital-art-collection-non-fungible-tokens): $6 Million
 
-All of them minted their NFTs using Alchemy’s powerful API. In this tutorial, we’ll teach you how to do the same in <10 minutes.
+All of them minted their NFTs using Alchemy’s powerful API. In this tutorial, we’ll teach you how to do the same in \<10 minutes.
 
 “Minting an NFT” is the act of publishing a unique instance of your ERC-721 token on the blockchain. Using our smart contract from [Part 1 of this NFT tutorial series](/developers/tutorials/how-to-write-and-deploy-an-nft/), let’s flex our Web3 skills and mint an NFT. At the end of this tutorial, you’ll be able to mint as many NFTs as your heart (and wallet) desires!