diff --git a/_chapters/08-ex5.md b/_chapters/08-ex5.md index e1df162..308e757 100644 --- a/_chapters/08-ex5.md +++ b/_chapters/08-ex5.md @@ -416,7 +416,7 @@ Case transformations are functions that act on `String`s and transform character | `uppercase()` | Converts the entire string to upper-case characters | `WE HOLD THESE TRUTHS TO BE SELF-EVIDENT` | | `lowercase()` | Converts the entire string to lower-case characters | `we hold these truths to be self-evident` | | `uppercasefirst()` | Converts the first character of the string to upper-case | `We hold these truths to be self-evident` | -| `lowercasefirst()` | Converts the first character of the string ot lower-case | `we hold these truths to be self-evident` | +| `lowercasefirst()` | Converts the first character of the string to lower-case | `we hold these truths to be self-evident` | ### Testing and attributes diff --git a/_chapters/11-ex8.md b/_chapters/11-ex8.md index 4286563..1e05e70 100644 --- a/_chapters/11-ex8.md +++ b/_chapters/11-ex8.md @@ -116,7 +116,7 @@ This structure is demonstrated by the following function, creating a resilient, end ``` -There is no need to specify a variable to hold the error instance. Similarly to not testing for the identity of the error, such a clause would result in a catch-all sequence. This is not necessarily a bad thing, but good code is responsive to the nature of errors, rather than their mere existence, and good programmers would always be interested in _why_ their code doesn't work, not merely in the fact that it failed to execute. Therefore, good code would check for the types of exceptions and only use catch-alls sparingly. +There is no need to specify a variable to hold the error instance. Similarly to not testing for the identity of the error, such a clause would result in a catch-all sequence. This is not necessarily a bad thing, but good code is responsive to the nature of errors, rather than their mere existence, and good programmers would always be interested in _why_ their code doesn't work, not merely in the fact that it failed to execute. Therefore, good code would check for the types of exceptions and only use catch-all sparingly. #### One-line `try`/`catch`