diff --git a/docs/markdown/Dependencies.md b/docs/markdown/Dependencies.md
index 401e019a3..faf410213 100644
--- a/docs/markdown/Dependencies.md
+++ b/docs/markdown/Dependencies.md
@@ -90,6 +90,16 @@ q5exe = executable('qt5test',
 
 Here we have an UI file created with Qt Designer and one source and header file each that require preprocessing with the `moc` tool. We also define a resource file to be compiled with `rcc`. We just have to tell Meson which files are which and it will take care of invoking all the necessary tools in the correct order, which is done with the `preprocess` method of the `qt5` module. Its output is simply put in the list of sources for the target. The `modules` keyword of `dependency` works just like it does with Boost. It tells which subparts of Qt the program uses.
 
+## Pcap
+
+The pcap library does not ship with pkg-config at the time or writing
+but instead it has its own `pcap-config` util. Meson will use it
+automatically:
+
+```meson
+pcap_dep = dependency('pcap', version : '>=1.0')
+```
+
 ## Declaring your own
 
 You can declare your own dependency objects that can be used interchangeably with dependency objects obtained from the system. The syntax is straightforward:
diff --git a/docs/markdown/Release-notes-for-0.42.0.md b/docs/markdown/Release-notes-for-0.42.0.md
index 54723410c..1ed74dc7a 100644
--- a/docs/markdown/Release-notes-for-0.42.0.md
+++ b/docs/markdown/Release-notes-for-0.42.0.md
@@ -131,3 +131,12 @@ like this:
 
 The old commands are still available but they are deprecated
 and will be removed in some future release.
+
+## Pcap dependency detector
+
+Meson will automatically obtain dependency information for pcap
+using the `pcap-config` tool. It is used like any other dependency:
+
+```meson
+pcap_dep = dependency('pcap', version : '>=1.0')
+```