From a27042c48508c8fc9417e9b0ab840549226f3bf7 Mon Sep 17 00:00:00 2001
From: kimg45 <138676274+kimg45@users.noreply.github.com>
Date: Sun, 29 Sep 2024 02:46:54 -0500
Subject: [PATCH] make commands more consistent

---
 content/posts/macos/macOS Security Overview.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/posts/macos/macOS Security Overview.md b/content/posts/macos/macOS Security Overview.md
index a5c4f2a..2ae0c24 100644
--- a/content/posts/macos/macOS Security Overview.md	
+++ b/content/posts/macos/macOS Security Overview.md	
@@ -32,7 +32,7 @@ You can check whether running processes are sandboxed in the Activity Monitor. R
 You can check whether an app is sandboxed and what entitlements it has *before* running it by running the command
 
 ``` zsh
-% codesign -dvvv --entitlements - <path to your app>
+codesign -dvvv --entitlements - <path to your app>
 ```
 
 If the app is sandboxed, you will see
@@ -54,7 +54,7 @@ Unlike the App Sandbox, the Hardened Runtime is required in order for an app to
 Check if an app is using the Hardened Runtime before running it with the command
 
 ``` zsh
-codesign --display --verbose /path/to/bundle.app
+codesign --display --verbose <path to your app>
 ```
 
 You will see `flags=0x10000(runtime)` if it's enabled.