From ad84fc1479a779faa3d8a893a11b566e7ae22b6c Mon Sep 17 00:00:00 2001 From: Ivan Molodetskikh Date: Sat, 27 Jul 2024 10:14:06 +0300 Subject: wiki: Fix em-dash --- wiki/Developing-niri.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'wiki') diff --git a/wiki/Developing-niri.md b/wiki/Developing-niri.md index 8fd93e89..47cbb143 100644 --- a/wiki/Developing-niri.md +++ b/wiki/Developing-niri.md @@ -52,7 +52,7 @@ We have integration with the [Tracy](https://github.com/wolfpld/tracy) profiler cargo build --release --features=profile-with-tracy-ondemand ``` -Then you can open Tracy (you will need the latest stable release) and attach to a running niri instance to collect profiling data. Profiling data is collected "on demand"---that is, only when Tracy is connected. You can run a niri build like this as your main compositor if you'd like. +Then you can open Tracy (you will need the latest stable release) and attach to a running niri instance to collect profiling data. Profiling data is collected "on demand"—that is, only when Tracy is connected. You can run a niri build like this as your main compositor if you'd like. > [!NOTE] > If you need to profile niri startup or the niri CLI, you can opt for "always on" profiling instead, using this feature flag: -- cgit