about summary refs log tree commit diff
diff options
context:
space:
mode:
authorGerd Zellweger <mail@gerdzellweger.com>2021-09-10 00:36:35 -0700
committerGitHub <noreply@github.com>2021-09-10 00:36:35 -0700
commit5d4d3bdc74dd7449421cc5208cffb73c75e40283 (patch)
treea644be6c44db3535cfb3b9873b93939146649287
parent497ee321af3b8496eaccd7af7b437f18bab81abf (diff)
downloadrust-5d4d3bdc74dd7449421cc5208cffb73c75e40283.tar.gz
rust-5d4d3bdc74dd7449421cc5208cffb73c75e40283.zip
Fix typo `option` -> `options`.
-rw-r--r--src/doc/unstable-book/src/library-features/asm.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/unstable-book/src/library-features/asm.md b/src/doc/unstable-book/src/library-features/asm.md
index a10928a7471..444b1cbf3cc 100644
--- a/src/doc/unstable-book/src/library-features/asm.md
+++ b/src/doc/unstable-book/src/library-features/asm.md
@@ -375,7 +375,7 @@ Any reuse of a named label, local or otherwise, can result in a assembler or lin
 
 As a consequence, you should only use GNU assembler **numeric** [local labels] inside inline assembly code. Defining symbols in assembly code may lead to assembler and/or linker errors due to duplicate symbol definitions.
 
-Moreover, on x86 when using the default intel syntax, due to [an llvm bug], you shouldn't use labels exclusively made of `0` and `1` digits, e.g. `0`, `11` or `101010`, as they may end up being interpreted as binary values. Using `option(att_syntax)` will avoid any ambiguity, but that affects the syntax of the _entire_ `asm!` block.
+Moreover, on x86 when using the default intel syntax, due to [an llvm bug], you shouldn't use labels exclusively made of `0` and `1` digits, e.g. `0`, `11` or `101010`, as they may end up being interpreted as binary values. Using `options(att_syntax)` will avoid any ambiguity, but that affects the syntax of the _entire_ `asm!` block.
 
 ```rust,allow_fail
 #![feature(asm)]