From 85440d024fff3f333887ab90ac613efd22cefbc9 Mon Sep 17 00:00:00 2001 From: Thor Adam Date: Mon, 18 Aug 2014 16:49:05 +0000 Subject: [PATCH] Fix typos --- Week01/2. REST.md | 2 +- Week01/3. ASP.NET Web API.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Week01/2. REST.md b/Week01/2. REST.md index 9d73fb7..60977a1 100644 --- a/Week01/2. REST.md +++ b/Week01/2. REST.md @@ -24,7 +24,7 @@ It is common to define a resource (such as /api/courses) which represents a list ## REST and HTTP ## Technically, REST doesn't depend on HTTP. However, most REST services are implemented using HTTP, and the reason for -that is that HTTP fits wery well, since all the main characteristics of REST are also prevalent in HTTP. +that is that HTTP fits very well, since all the main characteristics of REST are also prevalent in HTTP. It is therefore almost universal for REST services to use concepts from HTTP: diff --git a/Week01/3. ASP.NET Web API.md b/Week01/3. ASP.NET Web API.md index 85772a3..3b48f3c 100644 --- a/Week01/3. ASP.NET Web API.md +++ b/Week01/3. ASP.NET Web API.md @@ -4,7 +4,7 @@ In 2012, Microsoft released the first version of the [ASP.NET Web API](http://ww which was designed to create RESTful web services. Currently, this is Windows only. However, Microsoft is working on the next version, with the codename "ASP.NET vNext". -This version will unify all ASP.NET tecnhologies (Web Forms, MVC, Web API) into a single codebase, which will be +This version will unify all ASP.NET technologies (Web Forms, MVC, Web API) into a single codebase, which will be cross-platform. This version is [hosted on Github](https://github.com/aspnet). ## Architecture