Skip to content

Commit abe11b6

Browse files
authored
Merge pull request #667 from ehuss/fix-links
Fix some links.
2 parents 372c7f9 + 997f761 commit abe11b6

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

src/items/functions.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ extern "Rust" fn foo() {}
144144
```
145145

146146
Functions in Rust can be called by foreign code, and using an ABI that
147-
differs from Rust allows, for example, to provide functions that can be
147+
differs from Rust allows, for example, to provide functions that can be
148148
called from other programming languages like C:
149149

150150
```rust
@@ -156,7 +156,7 @@ extern "C" fn new_i32() -> i32 { 0 }
156156
extern "stdcall" fn new_i32_stdcall() -> i32 { 0 }
157157
```
158158

159-
Just as with [external block], when the `extern` keyword is used and the `"ABI`
159+
Just as with [external block], when the `extern` keyword is used and the `"ABI`
160160
is omitted, the ABI used defaults to `"C"`. That is, this:
161161

162162
```rust
@@ -306,7 +306,7 @@ async fn safe_example() {
306306
// An `unsafe` block is required to invoke the function initially:
307307
let p = 22;
308308
let future = unsafe { unsafe_example(&p) };
309-
309+
310310
// But no `unsafe` block required here. This will
311311
// read the value of `p`:
312312
let q = future.await;
@@ -360,7 +360,7 @@ attributes macros.
360360
[_Type_]: ../types.md#type-expressions
361361
[_WhereClause_]: generics.md#where-clauses
362362
[const context]: ../const_eval.md#const-context
363-
[external blocks]: external-blocks.md
363+
[external block]: external-blocks.md
364364
[path]: ../paths.md
365365
[block]: ../expressions/block-expr.md
366366
[variables]: ../variables.md

src/items/use-declarations.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -129,8 +129,8 @@ fn main() {}
129129
> use ::foo::baz::foobaz;
130130
> ```
131131
>
132-
> The 2015 edition does not allow use declarations to reference the [extern
133-
> prelude]. Thus [`extern crate`] declarations are still required in 2015 to
132+
> The 2015 edition does not allow use declarations to reference the [extern prelude].
133+
> Thus [`extern crate`] declarations are still required in 2015 to
134134
> reference an external crate in a use declaration. Beginning with the 2018
135135
> edition, use declarations can specify an external crate dependency the same
136136
> way `extern crate` can.

0 commit comments

Comments
 (0)