From 084722a1187bf6cbd03246b60172f6c97a6cc4bd Mon Sep 17 00:00:00 2001 From: Rett Berg Date: Wed, 6 Feb 2019 16:20:42 -0800 Subject: [PATCH] fix typos in cranelift-frontend/src/lib.rs --- cranelift/frontend/src/lib.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/cranelift/frontend/src/lib.rs b/cranelift/frontend/src/lib.rs index 7379503769..4cfb49939a 100644 --- a/cranelift/frontend/src/lib.rs +++ b/cranelift/frontend/src/lib.rs @@ -20,8 +20,8 @@ //! //! This API has been designed to help you translate your mutable variables into //! [`SSA`](https://en.wikipedia.org/wiki/Static_single_assignment_form) form. -//! [`use_var`](struct.FunctionBuilder.html#method.use_var) will returns the Cranelift IR value -//! that corresponds to your mutable variable at a precise point in the program. However, you know +//! [`use_var`](struct.FunctionBuilder.html#method.use_var) will return the Cranelift IR value +//! that corresponds to your mutable variable at a precise point in the program. However, if you know //! beforehand that one of your variables is defined only once, for instance if it is the result //! of an intermediate expression in an expression-based language, then you can translate it //! directly by the Cranelift IR value returned by the instruction builder. Using the @@ -30,7 +30,7 @@ //! beforehand if a variable is immutable or not). //! //! The moral is that you should use these three functions to handle all your mutable variables, -//! even those that are not present in the source code but artefacts of the translation. It is up +//! even those that are not present in the source code but artifacts of the translation. It is up //! to you to keep a mapping between the mutable variables of your language and their `Variable` //! index that is used by Cranelift. Caution: as the `Variable` is used by Cranelift to index an //! array containing information about your mutable variables, when you create a new `Variable`