commit - 38e2d6c75d65d770d518286e0f4abd7914719dfa
commit + 62f6cf63e48721f7c87cf4aa26ae6012ad09ada3
blob - a73f8a69a7a6d1ae510bd8dffc664126750e07d3
blob + bba3390d043a49aefa8519fab28cc0b0776b446e
--- Glossary.md
+++ Glossary.md
<strong><a id="Fuzz_Target" href="#Fuzz_Target">Fuzz Target</a></strong> (also **Target Function**, or **Fuzzing Target Function**, or **Fuzzing Entry Point**): A binary, a library, an API, or rather anything that can consume bytes for input and produce some sort of coverage data as an output. See the [libFuzzer documentation](https://llvm.org/docs/LibFuzzer.html#fuzz-target) for a more detailed explanation. A fuzz target is typically given the array of bytes by [libFuzzer](https://llvm.org/docs/LibFuzzer.html) or [AFL](http://lcamtuf.coredump.cx/afl/) for coverage guided fuzzing. Read more about good fuzzing target [here](https://github.com/google/fuzzing/blob/master/docs/good-fuzz-target.md).
-<strong><a id="Fuzzer" href="#Fuzzer">Fuzzer</a></strong>: The most overloaded term and used in a variety of contexts, which makes it bad. Sometimes, "Fuzzer" is referred to a [fuzz target](#Fuzz_target), a [fuzzing engine](#fuzzing_engine), a [mutation engine](#mutation-engine), a [test generator](#test-generator) or
-a [fuzzer build](#fuzzer-build).
+<strong><a id="Fuzzer" href="#Fuzzer">Fuzzer</a></strong>: The most overloaded term and used in a variety of contexts, which makes it bad. Sometimes, "Fuzzer" is referred to a [fuzz target](#Fuzz_target), a [fuzzing engine](#fuzzing_engine), a [mutation engine](#mutation_engine), a [test generator](#test_generator) or
+a [fuzzer build](#fuzzer_build).
<strong><a id="Fuzz_Input" href="#Fuzz_Input">Fuzz Input</a></strong>: A sequence of bytes that can be fed to a target. The input can be an arbitrary bag of bytes, or some structured data, e.g. serialized proto.
<strong><a id="Fuzz_Feature_Set" href="#Fuzz_Feature_Set">Fuzz Feature Set</a></strong>: A set of features associated with one specific input.
-<strong><a id="Fuzzer_build" href="#Fuzzer_build">Fuzzer Build</a></strong>: A build that contains all the fuzz targets for a given project, which is run with a specific fuzzing engine, in a specific build mode (e.g. with enabled/disabled assertions), and optionally combined with a sanitizer. In [OSS-Fuzz](https://google.github.io/oss-fuzz/), it is also known as a [job type](https://google.github.io/oss-fuzz/reference/glossary/#job-type).
+<strong><a id="Fuzzer_build" href="#Fuzzer_build">Fuzzer Build</a></strong>: A build that contains all the fuzz targets for a given project, which is run with a specific fuzzing engine, in a specific build mode (e.g. with enabled/disabled assertions), and optionally combined with a sanitizer.
<strong><a id="Fuzzing_Engine" href="#Fuzzing_Engine">Fuzzing Engine</a></strong>: A program that produces an infinite stream of inputs for a [fuzz target](#Fuzz_target) and orchestrates the execution. Examples: [libFuzzer](http://libfuzzer.info), [AFL](lcamtuf.coredump.cx/afl/), [honggfuzz](https://github.com/google/honggfuzz), etc. See related terms [Mutation Engine](#mutation_engine) and [Test Generator](#test_generator).
- (Fuzzing) https://github.com/google/centipede#terminology
- (Fuzzing) https://github.com/google/fuzzing/blob/master/docs/glossary.md
- (Fuzzing) https://google.github.io/clusterfuzz/reference/glossary/
-- (Fuzzing) https://google.github.io/oss-fuzz/reference/glossary/
- https://csrc.nist.gov/glossary glossary consists of terms and definitions extracted verbatim from NIST's cybersecurity- and privacy-related publications.
- https://xlinux.nist.gov/dads/ - Dictionary of Algorithms and Data Structures
-- [ISTQB Glossary](https://glossary.istqb.org/en_US/search)
+- [ISTQB Glossary](https://glossary.istqb.org/en_US/search) (Attention: some definitions are incorrect)
<!-- - https://github.com/ligurio/trash-software-bugs -->
\ No newline at end of file
