Skip to content

Commit 700c3ba

Browse files
committed
Fix typos in RFCs 501-750
1 parent 0177444 commit 700c3ba

6 files changed

+11
-11
lines changed

text/0517-io-os-reform.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1470,7 +1470,7 @@ Windows, it can be considered an optimization for `flush` and on
14701470
Windows behave identically to `sync_all`, just as it does on some Unix
14711471
filesystems.)
14721472

1473-
The `path` method wil remain `#[unstable]`, as we do not yet want to
1473+
The `path` method will remain `#[unstable]`, as we do not yet want to
14741474
commit to its API.
14751475

14761476
The `open_mode` function will be removed in favor of and will take an

text/0546-Self-not-sized-by-default.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ implemented):
3939
trait Foo for ?Sized { ... }
4040
```
4141

42-
This syntax doesn't have any other precendent in the language. One
42+
This syntax doesn't have any other precedent in the language. One
4343
might expect to write:
4444

4545
```rust

text/0550-macro-future-proofing.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ possible to lift these restrictions backwards compatibly if desired.
1212

1313
# Key Terminology
1414

15-
- `macro`: anything invokable as `foo!(...)` in source code.
15+
- `macro`: anything invocable as `foo!(...)` in source code.
1616
- `MBE`: macro-by-example, a macro defined by `macro_rules`.
1717
- `matcher`: the left-hand-side of a rule in a `macro_rules` invocation, or a subportion thereof.
1818
- `macro parser`: the bit of code in the Rust parser that will parse the input using a grammar derived from all of the matchers.
@@ -45,7 +45,7 @@ and `$foo` and `$i` are simple NT's with `expr` and `ident` as their
4545
respective fragment specifiers.
4646

4747
`$(i:ident),*` is *also* an NT; it is a complex NT that matches a
48-
comma-seprated repetition of identifiers. The `,` is the separator
48+
comma-separated repetition of identifiers. The `,` is the separator
4949
token for the complex NT; it occurs in between each pair of elements
5050
(if any) of the matched fragment.
5151

@@ -329,7 +329,7 @@ accordingly.
329329

330330
Below are some examples of FIRST and LAST.
331331
(Note in particular how the special ε element is introduced and
332-
eliminated based on the interation between the pieces of the input.)
332+
eliminated based on the interaction between the pieces of the input.)
333333

334334
Our first example is presented in a tree structure to elaborate on how
335335
the analysis of the matcher composes. (Some of the simpler subtrees

text/0599-default-object-bound.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ source today, but this has not been fully verified.)
147147

148148
# Detailed design
149149

150-
This section extends the high-level rule above with suppor for
150+
This section extends the high-level rule above with support for
151151
user-defined types, and also describes potential interactions with
152152
other parts of the system.
153153

@@ -243,7 +243,7 @@ the expansion of `Box<SomeTrait>` would be different.
243243

244244
**Interaction with object coercion.** The rules specify that `&'a
245245
SomeTrait` and `&'a mut SomeTrait` are expanded to `&'a
246-
(SomeTrait+'a)`and `&'a mut (SomeTrait+'a)` respecively. Today, in fn
246+
(SomeTrait+'a)`and `&'a mut (SomeTrait+'a)` respectively. Today, in fn
247247
signatures, one would get the expansions `&'a (SomeTrait+'b)` and `&'a
248248
mut (SomeTrait+'b)`, respectively. In the case of a shared reference
249249
`&'a SomeTrait`, this difference is basically irrelevant, as the

text/0639-discriminant-intrinsic.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ Note the returned values for two differently-typed variants may compare in any w
9393
simply treat them as single-variant enums and synthesise a zero constant. Note that this is what
9494
would be done for single-variant enums anyway.
9595

96-
* Do nothing. Improvements to codegen and/or optimisation could make this uneccessary. The
96+
* Do nothing. Improvements to codegen and/or optimisation could make this unnecessary. The
9797
"Sufficiently Smart Compiler" trap is a strong case against this reasoning though. There will
9898
likely always be cases where the user can write more efficient code than the compiler can produce.
9999

@@ -329,7 +329,7 @@ pub enum SqlState {
329329
FdwReplyHandle,
330330
FdwSchemaNotFound,
331331
FdwTableNotFound,
332-
FdwUnableToCreateExcecution,
332+
FdwUnableToCreateExecution,
333333
FdwUnableToCreateReply,
334334
FdwUnableToEstablishConnection,
335335
PlpgsqlError,

text/0738-variance.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Here the `Context` struct has one lifetime parameter, `data`, that
8686
represents the lifetime of some data that it references. Now let's
8787
imagine that the lifetime of the data is some lifetime we call
8888
`'x`. If we have a context `cx` of type `Context<'x>`, it is ok to
89-
(for example) pass `cx` as an argment where a value of type
89+
(for example) pass `cx` as an argument where a value of type
9090
`Context<'y>` is required, so long as `'x : 'y` ("`'x` outlives
9191
`'y`"). That is, it is ok to approximate `'x` as a shorter lifetime
9292
like `'y`. This makes sense because by changing `'x` to `'y`, we're
@@ -199,7 +199,7 @@ used in the body of the type. This generally occurs with unsafe code:
199199

200200
Since these parameters are unused, the inference can reasonably
201201
conclude that `AtomicPtr<int>` and `AtomicPtr<uint>` are
202-
interchangable: after all, there are no fields of type `T`, so what
202+
interchangeable: after all, there are no fields of type `T`, so what
203203
difference does it make what value it has? This is not good (and in
204204
fact we have behavior like this today for lifetimes, which is a common
205205
source of error).

0 commit comments

Comments
 (0)