Skip to content

Commit 402b128

Browse files
Havvyehuss
andauthored
Apply suggestions from code review
Co-authored-by: Eric Huss <[email protected]>
1 parent 31dc83f commit 402b128

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

src/expressions/await-expr.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
> &nbsp;&nbsp; [_Expression_] `.` `await`
66
77
*Await expressions* suspend the current computation until the given future is ready to produce a value.
8-
The syntax for an await expression is an expression with a type that implements the Future trait, called the *future operand*, then the token `.`, and then the `await` keyword.
8+
The syntax for an await expression is an expression with a type that implements the [Future] trait, called the *future operand*, then the token `.`, and then the `await` keyword.
99
Await expressions are legal only within an [async context], like an [`async fn`] or an [`async` block].
1010

1111
More specifically, an await expression has the following effect.

src/expressions/field-expr.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
A *field expression* is a [place expression] that evaluates to the location of a field of a [struct] or [union].
88
When the operand is [mutable], the field expression is also mutable.
99

10-
The syntax for a field expression is an expression, called the container operand*, then a `.`, and finally an [identifier].
10+
The syntax for a field expression is an expression, called the *container operand*, then a `.`, and finally an [identifier].
1111
Field expressions cannot be followed by a parenthetical comma-separated list of expressions, as that is instead parsed as a [method call expression].
1212
That is, they cannot be the function operand of a [call expression].
1313

0 commit comments

Comments
 (0)