From c43068c7c1da2fd5721544b189f0ab91a085d903 Mon Sep 17 00:00:00 2001 From: Stuart Ashenbrenner <72467868+stuartjash@users.noreply.github.com> Date: Thu, 25 Aug 2022 15:52:45 -0700 Subject: [PATCH] Update Readme.md --- Readme.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Readme.md b/Readme.md index ad9c607..eded990 100644 --- a/Readme.md +++ b/Readme.md @@ -53,8 +53,8 @@ sudo ./aftermath --analyze If deploying from an MDM solution, deploy a PPPC configuration profile with the Terminal given full disk access. You can then push a policy to deploy and trigger aftermath. -## Release -There is an Aftermath.pkg available under [Release](https://github.com/jamf/aftermath/releases). This pkg is signed and notarized. It will install the aftermath binary at `/usr/local/bin/`. This would be the ideal way to deploy via MDM. Since this is installed in `bin`, you can then run aftermath like +## Releases +There is an Aftermath.pkg available under [Releases](https://github.com/jamf/aftermath/releases). This pkg is signed and notarized. It will install the aftermath binary at `/usr/local/bin/`. This would be the ideal way to deploy via MDM. Since this is installed in `bin`, you can then run aftermath like ```bash sudo aftermath [option1] [option2] ```