Fix build error

content/0014_nft_metadata_refresh/readme.mdx

@@ -6,7 +6,7 @@ This allows a much wider range of data to be displayed, including enabling the u
 
 ## A Brief History
 
-ENS launched May 4, 2017, before both Curio Cards (May 9, 2017) and CryptoPunks (June 23, 2017). ([Check here to see if your .ETH name is “pre-Punks.”](https://medium.com/the-ethereum-name-service/do-you-have-an-og-ens-name-heres-a-new-tool-to-check-2bbe97900ce2))
+ENS launched May 4, 2017, before both Curio Cards (May 9, 2017) and CryptoPunks (June 23, 2017). ([Check here to see if your .ETH name is "pre-Punks."](https://medium.com/the-ethereum-name-service/do-you-have-an-og-ens-name-heres-a-new-tool-to-check-2bbe97900ce2))
 
 ERC-721 wouldn’t be released until later that year. ENS names were always by definition NFTs, but originally didn’t follow an NFT standard because none existed.
 
@@ -26,13 +26,13 @@ So we built EMS, the [ENS Metadata Service](https://github.com/ensdomains/ens-me
 
 _Note that this update has no effect on the ownership of names or their function in ENS. The core functions of ENS remain untouched and decentralized._
 
-If your name hasn’t refreshed on OpenSea yet and you can’t wait to see the new design for it, feel free to click the “Refresh metadata” button on the page for your name on OpenSea, wait a few minutes, then refresh the page.
+If your name hasn’t refreshed on OpenSea yet and you can’t wait to see the new design for it, feel free to click the "Refresh metadata" button on the page for your name on OpenSea, wait a few minutes, then refresh the page.
 
 We encourage other services to draw directly from our metadata service as well.
 
 This new metadata service accomplishes several important things:
 
-- **Puts the core ENS team and community in control of the metadata for ENS names for the first time** (see the “New Ideas” section below on how to suggest improvements)
+- **Puts the core ENS team and community in control of the metadata for ENS names for the first time** (see the "New Ideas" section below on how to suggest improvements)
 - Refresh of the default image for .ETH names
   ![](https://cdn-images-1.medium.com/max/1200/1*SV9wAaslu-wCL8ZJuKkVew.jpeg)
 
@@ -51,7 +51,7 @@ This shows an inval
 
 ## The Future
 
-We will be releasing an upgrade to ENS names soon we call the “[wrapper](https://github.com/ensdomains/name-wrapper)”. All newly created ENS names — whether they be .ETH 2LDs, subdomains, or DNS names imported into ENS — will be wrapped by default (with an opt-out available for advanced users). Owners of pre-wrapper names will be encouraged to upgrade their names (will require a transaction with gas unfortunately), but upgrading will always be optional and your name will still work just fine.
+We will be releasing an upgrade to ENS names soon we call the "[wrapper](https://github.com/ensdomains/name-wrapper)". All newly created ENS names — whether they be .ETH 2LDs, subdomains, or DNS names imported into ENS — will be wrapped by default (with an opt-out available for advanced users). Owners of pre-wrapper names will be encouraged to upgrade their names (will require a transaction with gas unfortunately), but upgrading will always be optional and your name will still work just fine.
 
 The wrapper will accomplish several important things:
 
@@ -73,7 +73,7 @@ Ideas we’ve had or heard from community members that would be possible to impl
 
 - allowing users to customize the colors of the background gradient
 - allowing users to set an image that completely replaces the NFT image (with no overlay of the ENS logo and name), which could enable ENS subdomains to be used to issue NFT artwork
-- signaling in some way a name is “pre-Punks”
+- signaling in some way a name is "pre-Punks"
 - marking 3 and 4 character .ETH names in some way given their rarity and higher price
 
 We want to hear from you on this. If you have ideas for ways the image or metadata can be improved, please share it in our [Discord](https://chat.ens.domains/).

content/0017_dns_on_mainnet/readme.mdx

@@ -2,7 +2,7 @@ We’re pleased to announce that full DNS namespace integration for [ENS](http:/
 
 This enables the owner of a DNS second-level domain name (a DNS name with one dot in it) to import the same name for use on ENS.
 
-For example, if you own “example.com” on DNS, you can import it into ENS — as example**.com**, not example**.eth**, the latter is a separate name. You can then set ENS records for it, e.g. to allow you to receive payments in cryptocurrencies like ETH, BTC, and DOGE to example.com.
+For example, if you own "example.com" on DNS, you can import it into ENS — as example**.com**, not example**.eth**, the latter is a separate name. You can then set ENS records for it, e.g. to allow you to receive payments in cryptocurrencies like ETH, BTC, and DOGE to example.com.
 
 → [Step-by-Step Guide to Importing a DNS Domain Name to ENS](https://support.ens.domains/en/articles/7882690-claim-your-dns-name)
 

content/0018_200_integrations/readme.mdx

@@ -1,6 +1,6 @@
 We’re pleased to announce the [Ethereum Name Service](https://ens.domains/) (ENS) is now integrated in more than 200 services!
 
-You can see the full list of integrations in the “[ENS Ecosystem](https://ens.domains/#home-ecosystem)” section of [our website](https://ens.domains/). There are also screenshots of that section as of this writing at the end of this post.
+You can see the full list of integrations in the "[ENS Ecosystem](https://ens.domains/#home-ecosystem)" section of [our website](https://ens.domains/). There are also screenshots of that section as of this writing at the end of this post.
 
 ![](https://cdn-images-1.medium.com/max/800/1*P9WQ5F0ubT5PMGq9bnXvRg.png)
 
@@ -30,12 +30,12 @@ There are many ways to utilize ENS in your service to improve UX, but here are t
   ![](https://cdn-images-1.medium.com/max/800/1*wp4iJIFe6CvUJ0h_aaLFwg.png)
   Voting on snapshot.org
 
-- **Dweb**: Want to decentralize your frontend? You can [host it on IPFS and point at it with ENS](https://medium.com/the-ethereum-name-service/cloudflare-and-fleek-make-ens-ipfs-site-deployment-as-easy-as-ever-262c990a7514). Your users have a [wide range of ways to access such websites](https://medium.com/the-ethereum-name-service/all-the-ways-you-can-surf-the-decentralized-web-today-bf8e7a42fa27), the easiest being just appending “.LINK” to the end, e.g. [almonit.eth.link](https://almonit.eth.link/#/).
+- **Dweb**: Want to decentralize your frontend? You can [host it on IPFS and point at it with ENS](https://medium.com/the-ethereum-name-service/cloudflare-and-fleek-make-ens-ipfs-site-deployment-as-easy-as-ever-262c990a7514). Your users have a [wide range of ways to access such websites](https://medium.com/the-ethereum-name-service/all-the-ways-you-can-surf-the-decentralized-web-today-bf8e7a42fa27), the easiest being just appending ".LINK" to the end, e.g. [almonit.eth.link](https://almonit.eth.link/#/).
   ![](https://cdn-images-1.medium.com/max/800/1*fXZSv8KqzfD4Jzrn7emtvg.png)
 
 ## Current Integrations
 
-Below are screenshots of the “[ENS Ecosystem](https://ens.domains/#home-ecosystem)” section on our website as of this writing. On [our website](https://ens.domains/#home-ecosystem), each icon is clickable to that project’s website.
+Below are screenshots of the "[ENS Ecosystem](https://ens.domains/#home-ecosystem)" section on our website as of this writing. On [our website](https://ens.domains/#home-ecosystem), each icon is clickable to that project’s website.
 
 ![](https://cdn-images-1.medium.com/max/800/1*-tj2aD-4BX31Ce_gYIaV2Q.png)
 ![](https://cdn-images-1.medium.com/max/800/1*BF3FsqYXGtQgcr2kTUr1mQ.png)