about summary refs log tree commit diff
diff options
context:
space:
mode:
authorYuki Okushi <huyuumi.dev@gmail.com>2020-12-30 18:15:18 +0900
committerGitHub <noreply@github.com>2020-12-30 18:15:18 +0900
commitb050261a1a54ee8afaed4e9e65f9558be81fd47b (patch)
tree08ad29d37a69ad2b12d44a7b0341b84e3e4913f5
parent30ddc91d41b1160a3a2594ea4a5fa6140a5186c1 (diff)
parent02db77c2d148a9a1ee51a5345beaa538225ff68b (diff)
downloadrust-b050261a1a54ee8afaed4e9e65f9558be81fd47b.tar.gz
rust-b050261a1a54ee8afaed4e9e65f9558be81fd47b.zip
Rollup merge of #80465 - eltociear:patch-3, r=jyn514
Fix typo in ffi-pure.md

accesing -> accessing
-rw-r--r--src/doc/unstable-book/src/language-features/ffi-pure.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/unstable-book/src/language-features/ffi-pure.md b/src/doc/unstable-book/src/language-features/ffi-pure.md
index 4aef4eeab55..236ccb9f905 100644
--- a/src/doc/unstable-book/src/language-features/ffi-pure.md
+++ b/src/doc/unstable-book/src/language-features/ffi-pure.md
@@ -31,7 +31,7 @@ parameters (e.g. pointers), globals, etc. `#[ffi_pure]` functions are not
 referentially-transparent, and are therefore more relaxed than `#[ffi_const]`
 functions.
 
-However, accesing global memory through volatile or atomic reads can violate the
+However, accessing global memory through volatile or atomic reads can violate the
 requirement that two consecutive function calls shall return the same value.
 
 A `pure` function that returns unit has no effect on the abstract machine's