Skip to content

Commit 511b497

Browse files
Merge pull request #177 from JordanSamhi/master
Fix: typo
2 parents 44bb5c4 + 865aaf6 commit 511b497

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

notebooks/FuzzingWithConstraints.ipynb

+1-1
Original file line numberDiff line numberDiff line change
@@ -686,7 +686,7 @@
686686
"metadata": {},
687687
"source": [
688688
"To express a minimum numeric value, we can use a more elegant way.\n",
689-
"The function `str.to_int()`, for instance, converts a string into an integer.\n",
689+
"The function `str.to.int()`, for instance, converts a string into an integer.\n",
690690
"To obtain a page size that of at least 100000, we can thus also write"
691691
]
692692
},

notebooks/Parser.ipynb

+1-1
Original file line numberDiff line numberDiff line change
@@ -517,7 +517,7 @@
517517
"source": [
518518
"## Using a Parser\n",
519519
"\n",
520-
"Generally speaking, a _parser_ is the part of a a program that processes (structured) input. The parsers we discuss in this chapter transform an input string into a _derivation tree_ (discussed in the [chapter on efficient grammar fuzzing](GrammarFuzzer.ipynb)). From a user's perspective, all it takes to parse an input is two steps: \n",
520+
"Generally speaking, a _parser_ is the part of a program that processes (structured) input. The parsers we discuss in this chapter transform an input string into a _derivation tree_ (discussed in the [chapter on efficient grammar fuzzing](GrammarFuzzer.ipynb)). From a user's perspective, all it takes to parse an input is two steps: \n",
521521
"\n",
522522
"1. Initialize the parser with a grammar, as in\n",
523523
"```\n",

0 commit comments

Comments
 (0)