summaryrefslogtreecommitdiff
path: root/exercises/lifetimes/README.md
diff options
context:
space:
mode:
authorAli Afsharzadeh <afsharzadeh8@gmail.com>2023-03-30 19:53:22 +0330
committerAli Afsharzadeh <afsharzadeh8@gmail.com>2023-03-30 19:53:22 +0330
commit382e16eb7ea66cddc4860f4b19453b031a2a8a8a (patch)
tree4867f505b36ed69381a294b58d056cd9e92b8439 /exercises/lifetimes/README.md
parent362c1b0d113ad9a5bd4d1dee8086757efd060785 (diff)
feat(docs): add markdown linter for exercises README.md files
Diffstat (limited to 'exercises/lifetimes/README.md')
-rw-r--r--exercises/lifetimes/README.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/exercises/lifetimes/README.md b/exercises/lifetimes/README.md
index 74a4a78..91373f7 100644
--- a/exercises/lifetimes/README.md
+++ b/exercises/lifetimes/README.md
@@ -3,17 +3,17 @@
Lifetimes tell the compiler how to check whether references live long
enough to be valid in any given situation. For example lifetimes say
"make sure parameter 'a' lives as long as parameter 'b' so that the return
-value is valid".
+value is valid".
-They are only necessary on borrows, i.e. references,
+They are only necessary on borrows, i.e. references,
since copied parameters or moves are owned in their scope and cannot
be referenced outside. Lifetimes mean that calling code of e.g. functions
-can be checked to make sure their arguments are valid. Lifetimes are
+can be checked to make sure their arguments are valid. Lifetimes are
restrictive of their callers.
-If you'd like to learn more about lifetime annotations, the
-[lifetimekata](https://tfpk.github.io/lifetimekata/) project
-has a similar style of exercises to Rustlings, but is all about
+If you'd like to learn more about lifetime annotations, the
+[lifetimekata](https://tfpk.github.io/lifetimekata/) project
+has a similar style of exercises to Rustlings, but is all about
learning to write lifetime annotations.
## Further information