From 2377fcbf3476c49973fcc4ce5120e4810bee5ae5 Mon Sep 17 00:00:00 2001
From: Simon McVittie <smcv@collabora.com>
Date: Tue, 2 Jun 2020 15:41:11 +0100
Subject: [PATCH] bwrap-lock: Correct doc-comment

At some point while I was designing this, the @path was a directory,
but it ended up being a file.

Fixes: 8b531350 "wrap: Add API for a bubblewrap-compatible fcntl lock"
Signed-off-by: Simon McVittie <smcv@collabora.com>
---
 src/bwrap-lock.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/bwrap-lock.c b/src/bwrap-lock.c
index 664b61f22..991f1e73f 100644
--- a/src/bwrap-lock.c
+++ b/src/bwrap-lock.c
@@ -55,11 +55,11 @@ struct _PvBwrapLock
 
 /**
  * pv_bwrap_lock_new:
- * @path: Runtime directory to lock; the actual lock file will be `$path/.ref`
- * @flags: Flags affecting how we lock the directory
+ * @path: File to lock
+ * @flags: Flags affecting how we lock the file
  * @error: Used to raise an error on failure
  *
- * Take out a lock on a directory.
+ * Take out a lock on a file.
  *
  * If %PV_BWRAP_LOCK_FLAGS_WRITE is in @flags, the lock is a write-lock,
  * which can be held by at most one process at a time. This is appropriate
-- 
GitLab