Skip to content

Commit c138c99

Browse files
Merge pull request #385 from danielquinn/gh-pages
Fix a few grammatical issues
2 parents 40bd025 + 838a875 commit c138c99

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

python/lesson4/tutorial.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ function that returns a value:
105105
... return "My name is " + name
106106

107107
Now the function returns a value that we can work with. We could store this in
108-
a value to be used later. Let's try storing it as a value, and using that value
108+
a variable to be used later. Let's try storing it as a value, and using that value
109109
as a parameter in another `print()` function call.
110110

111111
>>> statement = get_statement("Lisa")
@@ -118,7 +118,7 @@ script, simply calling the function without a print statement would not print
118118
anything to the screen. This is because the function is returning a value, and
119119
no longer printing a string.
120120

121-
A subtle indicator of this is the quote marks around the sentence that denotes
121+
A subtle indicator of this are the quote marks around the sentence that denotes
122122
a string is being output to the screen, rather than something being printed
123123
with the print function:
124124

@@ -128,7 +128,7 @@ with the print function:
128128

129129
## Why use functions
130130

131-
At first glance it may not seem obvious why it is worth expending the extra
131+
At first glance it may not seem obvious why it's worth expending the extra
132132
effort of defining and calling a function, rather than just writing the code
133133
independent of such things. Defining tasks as functions reduces the need to
134134
copy and paste the same code multiple times to achieve the same effect. Simply

0 commit comments

Comments
 (0)