Skip to content

Commit 036e88a

Browse files
committed
Fix some links and small wordings
1 parent 704f045 commit 036e88a

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

src/ch19-01-unsafe-rust.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -442,7 +442,7 @@ The final action that works only with `unsafe` is accessing fields of a
442442
used in a particular instance at one time. Unions are primarily used to
443443
interface with unions in C code. Accessing union fields is unsafe because Rust
444444
cant guarantee the type of the data currently being stored in the union
445-
instance. You can learn more about unions in [the reference][reference].
445+
instance. You can learn more about unions in [the Rust Reference][reference].
446446
447447
### When to Use Unsafe Code
448448

src/ch19-06-macros.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ pub fn some_name(input: TokenStream) -> TokenStream {
182182
}
183183
```
184184

185-
<span class="caption">Listing 19-29: An example of using a procedural
185+
<span class="caption">Listing 19-29: An example of defining a procedural
186186
macro</span>
187187

188188
The function that defines a procedural macro takes a `TokenStream` as an input
@@ -484,11 +484,11 @@ Function-like macros define macros that look like function calls. Similarly to
484484
`macro_rules!` macros, they’re more flexible than functions; for example, they
485485
can take an unknown number of arguments. However, `macro_rules!` macros can be
486486
defined only using the match-like syntax we discussed in the section
487-
[“Declarative Macros with `macro_rules!` for General Metaprogramming”][decl]
488-
earlier. Function-like macros take a `TokenStream` parameter and their
489-
definition manipulates that `TokenStream` using Rust code as the other two
490-
types of procedural macros do. An example of a function-like macro is an `sql!`
491-
macro that might be called like so:
487+
[“Declarative Macros with `macro_rules!` for General
488+
Metaprogramming”][decl]<!-- ignore --> earlier. Function-like macros take a
489+
`TokenStream` parameter and their definition manipulates that `TokenStream`
490+
using Rust code as the other two types of procedural macros do. An example of a
491+
function-like macro is an `sql!` macro that might be called like so:
492492

493493
[decl]: #declarative-macros-with-macro_rules-for-general-metaprogramming
494494

0 commit comments

Comments
 (0)