add note regarding my experience with EV+OV certs (tauri-apps#927)

* add note about EV+OV certs

* wording

* fix: link style and minor rephrasing

* fix: typo

* fix: another typo, sorryyy

Co-authored-by: Fabian-Lars <[email protected]>

Author: goenning

docs/guides/distribution/sign-windows.md

@@ -15,6 +15,14 @@ Code signing your application lets users know that they downloaded the official
 - Code signing certificate - you can acquire one of these on services such as Digicert.com, Comodo.com, & Godaddy.com. In this guide, we are using Comodo.com
 - A working Tauri application
 
+:::note
+
+If you sign the app with an EV Certificate, it'll receive immediate reputation with Microsoft SmartScreen and won't show any warnings to users.
+
+If you opt for an OV Certificate, which is generally cheaper and available to individuals, Microsoft SmartScreen will still show a warning to users when they download the app. It might take some time until your certificate builds enough reputation. You may opt for [submitting your app] to Microsoft for manual review. Although not guaranteed, if the app does not contain any malicious code, Microsoft may grant additional reputation and potentially remove the warning for that specific uploaded file.
+
+:::
+
 ## Getting Started
 
 There are a few things we have to do to get Windows prepared for code signing. This includes converting our certificate to a specific format, installing this certificate, and decoding required information from the certificate.
@@ -176,5 +184,6 @@ jobs:
 
 5. Your workflow can now import your windows certificate and import it into the GitHub runner, allowing for automated code-signing!
 
+[submitting your app]: https://www.microsoft.com/en-us/wdsi/filesubmission/
 [encrypted secrets]: https://docs.github.com/en/actions/reference/encrypted-secrets
 [`tauri-action` publish template]: https://github.com/tauri-apps/tauri-action