Merge #305

bors[bot] · rwaskiewicz · web-flow · commit 51739471276b · 2021-10-17T16:48:42.000Z
305: Fix typo in 'The Borrow Checker' r=eldruin a=rwaskiewicz

'luckliy' -&gt; 'luckily'

Co-authored-by: Ryan Waskiewicz &lt;ryanwaskiewicz@gmail.com&gt;
diff --git a/src/peripherals/borrowck.md b/src/peripherals/borrowck.md
@@ -16,4 +16,4 @@ The last two of these rules sound suspiciously similar to what the Borrow Checke
 
 Imagine if we could pass around ownership of these peripherals, or offer immutable or mutable references to them?
 
-Well, we can, but for the Borrow Checker, we need to have exactly one instance of each peripheral, so Rust can handle this correctly. Well, luckliy in the hardware, there is only one instance of any given peripheral, but how can we expose that in the structure of our code?
+Well, we can, but for the Borrow Checker, we need to have exactly one instance of each peripheral, so Rust can handle this correctly. Well, luckily in the hardware, there is only one instance of any given peripheral, but how can we expose that in the structure of our code?

Original file line number	Diff line number	Diff line change
`@@ -16,4 +16,4 @@ The last two of these rules sound suspiciously similar to what the Borrow Checke`
`16`	`16`
`17`	`17`	`Imagine if we could pass around ownership of these peripherals, or offer immutable or mutable references to them?`
`18`	`18`
`19`		`-Well, we can, but for the Borrow Checker, we need to have exactly one instance of each peripheral, so Rust can handle this correctly. Well, luckliy in the hardware, there is only one instance of any given peripheral, but how can we expose that in the structure of our code?`
	`19`	`+Well, we can, but for the Borrow Checker, we need to have exactly one instance of each peripheral, so Rust can handle this correctly. Well, luckily in the hardware, there is only one instance of any given peripheral, but how can we expose that in the structure of our code?`