Fix linter warnings in 3.0 post

website/src/_posts/2022-09-3.0.md

@@ -12,7 +12,7 @@ published: true
 
 ![Screenshot of Uppy 3.0.0 UI](/images/blog/3.0/uppy-3-0.png)
 
-Uppy is turning three! Of course, when you're counting in [dog years](https://www.akc.org/expert-advice/health/how-to-calculate-dog-years-to-human-years/) – which we most certainly are – that's 29 already. An age like that signifies proper adulthood. For Uppy, this means it’s ready to stay loyal, but without the silly mistakes (read: bugs). Uppy also underwent (ESM) surgery to keep it strolling by your side in the current ecosystem, and received other behavioral improvements 🐶
+Uppy is turning three! When you’re counting in [dog years](https://www.akc.org/expert-advice/health/how-to-calculate-dog-years-to-human-years/) – which we most certainly are – that’s 29 already. An age like that signifies proper adulthood. For Uppy, this means it’s ready to stay loyal, but without the silly mistakes (read: bugs). Uppy also underwent (ESM) surgery to keep it strolling by your side in the current ecosystem, and received other behavioral improvements 🐶
 
 TL;DR: ESM transition, native mobile camera, new Remote Sources plugin, sweeping Companion rewrite and streaming support, `async`/`await` everything, React 18 and Vue 3 support, all examples rewritten.
 
@@ -22,9 +22,9 @@ TL;DR: ESM transition, native mobile camera, new Remote Sources plugin, sweeping
 
 [ECMAScript Modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules) (ESM) are the future and we’re ready to adopt it. Benefits over CommonJS include: improved security, better tree shaking, and a syntax that can be understood natively by browsers, which can greatly improve the DX if the tools are configured to take advantage of that.
 
-Following in the footsteps of many other packages, we now exclusively ship Uppy core and its plugins as ESM. For Uppy 2.x, we were shipping CommonJS.
+Following in the footsteps of many other packages, we now only ship Uppy core and its plugins as ESM. For Uppy 2.x, we were shipping CommonJS.
 
-If you are already using ESM or the CDN builds, nothing changes for you! If you are using CommonJS, you may have to add additional tooling for everything to work, or consider refactoring your codebase to ESM. Please refer to the [Pure ESM package gist](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c) for more information and help on how to do that.
+If you are already using ESM or the CDN builds, nothing changes for you! If you are using CommonJS, you may have to add extra tooling for everything to work, or consider refactoring your codebase to ESM. Please refer to the [Pure ESM package gist](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c) for more information and help on how to do that.
 
 ## Less integration code with the new remote sources preset
 
@@ -59,9 +59,9 @@ It did, however, come with its own set of new problems:
 
 * Robodog tries to do the exact same thing as Uppy, but looks like an entirely different product.
 * Users are faced with a confusing choice between using Robodog or using Uppy directly.
-* Robodog is more ergonomic because it is limited. When hitting such a limit, the user has to refactor everything to Uppy using plugins.
+* Robodog is more ergonomic because it’s limited. When hitting such a limit, the user has to refactor everything to Uppy using plugins.
 
-This has now led us to deprecating Robodog and embracing Uppy for its strong suits: modularity and flexibility. At the same time, we're also introducing something to take away some of the repetitive integration code: [`@uppy/remote-sources`](/docs/remote-sources).
+This has now led us to deprecating Robodog and embracing Uppy for its strong suits: modularity and flexibility. At the same time, we’re also introducing something to take away some of the repetitive integration code: [`@uppy/remote-sources`](/docs/remote-sources).
 
 Are you using Robodog in your code base? You can check out the [migration guide](https://uppy.io/docs/migration-guides.html#Migrate-from-Robodog-to-Uppy-plugins) to see how you can transition to Uppy plugins without losing functionality. We have committed ourselves to extending Robodog support for one year to give our users more time to migrate.
 
@@ -77,7 +77,7 @@ uppy.use(Webcam, {
 })
 ```
 
-By default, it uses the [`is-mobile`](https://github.com/juliangruber/is-mobile) package to detect mobile devices, like smartphones and tablets, but you can manually set this option to `true` or `false` if you wish. When enabled, instead of the usual Camera/Webcam Uppy UI, users will be presented with buttons that open their device's native camera interface:
+By default, it uses the [`is-mobile`](https://github.com/juliangruber/is-mobile) package to detect mobile devices, like smartphones and tablets, but you can manually set this option to `true` or `false` if you wish. When enabled, instead of the usual Camera/Webcam Uppy UI, users will be presented with buttons that open their device’s native camera interface:
 
 ![Uppy native camera UI](/images/blog/3.0/native-camera.jpg)
 
@@ -107,7 +107,7 @@ Streaming upload can now also be enabled in Companion when using Tus. This comes
 
 With streaming upload disabled (default), the whole file will be downloaded first. The upload will then start when the download has completely finished.
 
-When streaming upload is enabled, Companion will start downloading the file from the provider (e.g., Google Drive), while at the same time starting the upload to the destination (e.g., Tus), and sending every chunk of data consecutively.
+When streaming upload is enabled, Companion will start downloading the file from the provider (such as Google Drive), while at the same time starting the upload to the destination (such as Tus), and sending every chunk of data consecutively.
 
 For more information, see the [Companion docs](/docs/companion/).
 
@@ -155,4 +155,4 @@ We have also replaced the deprecated [`request`](https://github.com/request/requ
 
 For more details, see the full [changelog](https://github.com/transloadit/uppy/blob/HEAD/CHANGELOG.md#1300) and the [migration guide](/docs/migration-guides.html).
 
-That's it from us for now! As you can see, Uppy may be slowly turning into an old dog, but we're still committed to keep teaching it new tricks. We hope you'll enjoy this latest major release, and all of the features and improvements it includes. We can't wait to hear your thoughts about it on [Twitter](https://twitter.com/uppy_io)!
+That’s it from us for now! As you can see, Uppy may be slowly turning into an old dog, but we’re still committed to keep teaching it new tricks. We hope you’ll enjoy this latest major release, and all the features and improvements it includes. We can’t wait to hear your thoughts about it on [Twitter](https://twitter.com/uppy_io)!