about summary refs log tree commit diff
diff options
context:
space:
mode:
authorintrigus-lgtm <60750685+intrigus-lgtm@users.noreply.github.com>2024-09-06 23:26:03 +0200
committerGitHub <noreply@github.com>2024-09-06 23:26:03 +0200
commit60d3ecab637ce492bb9cb39d479f1ae094f2795d (patch)
treea8287bda082df72ab1e9bab292d7f64c805aaaa5
parentd0f39849c2c5d2dc4be74b7abe3f59d1722e2102 (diff)
downloadafl++-60d3ecab637ce492bb9cb39d479f1ae094f2795d.tar.gz
Fix broken link in CONTRIBUTING.md (#2196)
* Fix broken link in CONTRIBUTING.md

* Also change link text
-rw-r--r--CONTRIBUTING.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8b4dcb6d..40f11ce8 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -48,7 +48,7 @@ When working on the docs, please keep the following guidelines in mind:
   * Don't: fuzzing-network-service.md
 * Use a maximum of 80 characters per line to make reading in a console easier.
 * Make all pull requests against `dev`, see
-  [#how-to-submit-a-pull-request-to-afl](#how-to-submit-a-pull-request-to-afl).
+  [#how-to-submit-a-pull-request](#how-to-submit-a-pull-request).
 
 And finally, here are some best practices for writing docs content:
 
@@ -57,4 +57,4 @@ And finally, here are some best practices for writing docs content:
 * Use bulleted lists to present similar content in a way that makes it easy to
   scan.
 * Use numbered lists for procedures or prioritizing.
-* Link to related content, for example, prerequisites or in-depth discussions.
\ No newline at end of file
+* Link to related content, for example, prerequisites or in-depth discussions.