Skip to content

Commit 7541e17

Browse files
committed
fix typos
1 parent ec954a9 commit 7541e17

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

content/docs/fuzzing/_index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -221,10 +221,10 @@ Note, that the two just mentioned sanitizers introduce instrumentation with the
221221
What type of issues fuzzing can find?
222222

223223
* Crashes and panics
224-
* Memory corruption issues: UAFs, integer overflows, undefined behaviors, buffer overflows, memory leaks etc
224+
* Memory corruption issues: UAFs, integer overflows, undefined behaviors, buffer overflows, memory leaks, etc.
225225

226226
* Invariant violations: business logic bugs
227-
* State invariants violations: properties that require statefull fuzzing
227+
* State invariants violations: properties that require stateful fuzzing
228228

229229
* Differentials: cross testing between different implementations of the same functionality
230230
* Cross-platform differentials: testing the same code on different architectures

content/docs/static-analysis/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This section presents several static analysis tools. For each tool, we cover top
1919

2020
Below is an overview of techniques implemented in static analysis tools.
2121

22-
Usually tools support only a subset of the following analyses, with varying degree of precision and completeness. Knowing what are a tool's capabilities is useful in determining it's usefulness.
22+
Usually, tools support only a subset of the following analyses, with varying degrees of precision and completeness. Knowing what a tool's capabilities are is important in determining its usefulness.
2323

2424
### Views on a code
2525

0 commit comments

Comments
 (0)