aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIvan Molodetskikh <yalterz@gmail.com>2024-07-27 10:14:06 +0300
committerIvan Molodetskikh <yalterz@gmail.com>2024-07-27 10:14:06 +0300
commitad84fc1479a779faa3d8a893a11b566e7ae22b6c (patch)
tree5e61c772cbf709c2e38febfad11c297c86109318
parentd5a8074b5388518871a949093e34f44d735157e7 (diff)
downloadniri-ad84fc1479a779faa3d8a893a11b566e7ae22b6c.tar.gz
niri-ad84fc1479a779faa3d8a893a11b566e7ae22b6c.tar.bz2
niri-ad84fc1479a779faa3d8a893a11b566e7ae22b6c.zip
wiki: Fix em-dash
-rw-r--r--wiki/Developing-niri.md2
1 files changed, 1 insertions, 1 deletions
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: