Fix MS product name

soong-construction · Jul 28, 2020 · 1e48374 · 1e48374
1 parent d852e9c
commit 1e48374
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -55,7 +55,7 @@ In order to consolidate the database, the tool prepares update scripts for you,
 
 ## Troubleshooting
 Starting:
-- to understand Windows SmartScreen Defender warnings for *dirt-rally-time-recorder*, read [this](docs/unknown-publisher-warning.md)
+- to understand MS Defender SmartScreen warnings for *dirt-rally-time-recorder*, read [this](docs/unknown-publisher-warning.md)
 - if you encounter an error message about sockets, understand that this tool cannot run in parallel, but only in a single instance at the same time
 - unless you downloaded the bundled version, have a look at `resources/migrate.sql` to find instructions how to update to new releases
 - if you encounter errors at start-up, see if renaming the file `dirtrally-laptimes.db` helps (which will create a new database) 

diff --git a/docs/unknown-publisher-warning.md b/docs/unknown-publisher-warning.md
@@ -1,6 +1,6 @@
 ## Trusting the executable
 
-When running this program from the pre-built .exe, Windows SmartScreen Defender might warn you about an unknown publisher or untrusted certificate. This is expected, as the executable is signed with the author's personal self-signed certificate. Properly signing with a root certificate trusted by Windows and other operating systems is costly and requires funding that this project does not have. 
+When running this program from the pre-built .exe, MS Defender SmartScreen might warn you about an unknown publisher or untrusted certificate. This is expected, as the executable is signed with the author's personal self-signed certificate. Properly signing with a root certificate trusted by Windows and other operating systems is costly and requires funding that this project does not have. 
 
 You should still check the `timerecord.exe` and verify it's actually original. To this end, it has been signed with a certificate that is described in the next section. To ensure your `timerecord.exe` has not been tampered with, open its certificate by viewing its properties through the context menu. Navigate to Digital Signatures, then Details, select View Certificate, then again Details (cf. screenshots in German Locale).