small typo fixes

web-apps-for-everyone/02-progressive-enhancement.md

@@ -44,7 +44,7 @@ When working on your own applications, try to perform the same exercise First, d
 
 ## Is progressive enhancement still relevant?
 
-Some may question how relative progressive enhancement is today, when a small percentage of user's browse the web with JavaScript disabled[^1]. This places the focus too heavily on progressive enhancement as a JavaScript free version of a site. In fact, some types of applications, such as video chat, absolutely require some form of JavaScript to work in the browser. The goal of progressive enhancement is to provide the absolute minimum for a working product and ensure that it is delivered to user's browser.
+Some may question how relative progressive enhancement is today, when a small percentage of users browse the web with JavaScript disabled[^1]. This places the focus too heavily on progressive enhancement as a JavaScript free version of a site. In fact, some types of applications, such as video chat, absolutely require some form of JavaScript to work in the browser. The goal of progressive enhancement is to provide the absolute minimum for a working product and ensure that it is delivered to user's browser.
 
 Ideally, this working minimum product is simply HTML without any external resources such as images, video CSS, or JavaScript. When a user's browser requests our site we can be certain that they will receive HTML (or nothing at all). By creating a working version of our application, even with a minimal experience, using the smallest number of assets, we can be sure that the user is able to access our content in some form.
 
@@ -137,7 +137,7 @@ For JavaScript dependent applications we could render the landing page as HTML o
 <link rel="prefetch" href=“app.js”>
 ```
 
-This allows gives our user's the opportunity to download and cache the application's JavaScript, without impacting the performance or requirement on a mostly static page. Soon browsers will begin implementing the [Preload specification](https://w3c.github.io/preload/), which will be similar to Prefetch, but enable additional browser features.
+This approach gives our user's the opportunity to download and cache the application's JavaScript, without impacting the performance or requirement on a mostly static page. Soon browsers will begin implementing the [Preload specification](https://w3c.github.io/preload/), which will be similar to Prefetch, but enable additional browser features.
 
 In action preload looks similar to prefetch:
 

web-apps-for-everyone/03-accessibility.md

@@ -265,7 +265,7 @@ Here are a few tips for writing semantic and useful HTML:
 - Make use of HTML5 content tags such as `<header>`, `<nav>`, `<main>`, `<footer>`, and `<aside>`.
 - Mark up the HTML content in the order you would expect the user to read it and use CSS to change the order appearance when necessary. 
 - Use semantic heading tags that follow a clear outline of page content and avoid using styled paragraphs or other elements as headers.
-- Use `<label>` elements to associate the label of form field with it’s input element.
+- Use `<label>` elements to associate the label of form field with its input element.
 - Always provide alternate text for images using the alt attribute. When an image is purely decorative, give the alt attribute an empty value (`alt=“”`) so that screen readers know to ignore it.
 
 ### ARIA