Merge pull request #503 from plausible/fix-random-typos

Fix typos

Author: metmarkosaric

docs/custom-event-goals.md

@@ -160,7 +160,7 @@ Once you have this script inserted on your page, Plausible will be able to track
 
 </h3>
 
-If you want to track multiple elements accross your site, you can use the same code from step 3 on all of your pages. The only modification you will have to make, is list as many pairs of `elementId` and `classes` as you want. For example, if you want to track three elements:
+If you want to track multiple elements across your site, you can use the same code from step 3 on all of your pages. The only modification you will have to make, is list as many pairs of `elementId` and `classes` as you want. For example, if you want to track three elements:
 
 ```javascript
 var toTag = [

docs/google-analytics-import.md

@@ -42,7 +42,7 @@ We also have measures in place to detect and avoid double-counting visitors if y
 2. You do the first Google Analytics import into that Plausible dashboard and choose your old UA property. We automatically import the data from when you started using that UA property until you stopped using it (say Oct 25th 2008 to May 19th 2023)
 3. Then you do the second Google Analytics import into that Plausible dashboard and this time you choose your newer GA4 property. We automatically import the data from when you stopped using UA until you started using Plausible (May 19th 2023 to Mar 11th 2024)
 
-This makes it easy and convenient to import all your historical Google Analytics stats from multiple properties without having any gaps in your data and without any double-counting. It also allows you the flexibility to choose the order in which you import your historical properties into Plausible. For instance, if you've used GA4 and UA simultanously for some time, you can choose which data you prefer to keep in Plausible and import that specific property first. The second import will cover the missing date ranges and will not overwrite the first import.
+This makes it easy and convenient to import all your historical Google Analytics stats from multiple properties without having any gaps in your data and without any double-counting. It also allows you the flexibility to choose the order in which you import your historical properties into Plausible. For instance, if you've used GA4 and UA simultaneously for some time, you can choose which data you prefer to keep in Plausible and import that specific property first. The second import will cover the missing date ranges and will not overwrite the first import.
 
 :::tip Do you want your Google Analytics data to replace the native Plausible data up to today?
 This isn't recommended as the native data is superior to the imported data but it's possible if you wish to do so. You can [reset the Plausible stats](reset-site-data.md) first and make the import after that

docs/proxy/guides/deno.md

@@ -46,7 +46,7 @@ This will deploy a new project and present an online text editor with the conten
 
 ### Using Deno's runtime CLI
 
-Assumming you have a local installation of the [Deno runtime](https://docs.deno.com/runtime/manual#install-deno), initialize a new project with the init command:
+Assuming you have a local installation of the [Deno runtime](https://docs.deno.com/runtime/manual#install-deno), initialize a new project with the init command:
 
 ```shell
 deno init proxy-project-folder