Correct malware blog's slug (#3046)

<!-- PR description-->

---

#### Does this PR need a docs update or release note?

- [ ]  Yes, it's included
- [ ] 🕐 Yes, but in a later PR
- [ ]  No

#### Type of change

<!--- Please check the type of change your PR introduces: --->
- [ ] 🌻 Feature
- [ ] 🐛 Bugfix
- [ ] 🗺️ Documentation
- [ ] 🤖 Supportability/Tests
- [ ] 💻 CI/Deployment
- [ ] 🧹 Tech Debt/Cleanup

#### Issue(s)

<!-- Can reference multiple issues. Use one of the following "magic words" - "closes, fixes" to auto-close the Github issue. -->
* #<issue>

#### Test Plan

<!-- How will this be tested prior to merging.-->
- [ ] 💪 Manual
- [ ]  Unit test
- [ ] 💚 E2E
This commit is contained in:
Nočnica Mellifera 2023-04-11 10:30:48 -07:00 committed by GitHub
parent cae3debd28
commit 4eef3d3703
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -1,5 +1,5 @@
--- ---
slug: malware-detection slug: microsoft-365-malware-detection-and-your-responsibilities
title: "Microsoft 365, Malware 👾, and your responsibilities" title: "Microsoft 365, Malware 👾, and your responsibilities"
description: "When we evaluate malware threats, we often think mainly of protecting our users. description: "When we evaluate malware threats, we often think mainly of protecting our users.
The biggest concern is always going to be lost availability and leaked data if The biggest concern is always going to be lost availability and leaked data if