From e37b35b211587a501633f0d65f6c6d1758904076 Mon Sep 17 00:00:00 2001 From: Carson Gross Date: Mon, 18 Jul 2022 11:45:19 -0600 Subject: [PATCH] clean up --- .../how-did-rest-come-to-mean-the-opposite-of-rest.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/www/essays/how-did-rest-come-to-mean-the-opposite-of-rest.md b/www/essays/how-did-rest-come-to-mean-the-opposite-of-rest.md index 1c775e7b..5b12f542 100644 --- a/www/essays/how-did-rest-come-to-mean-the-opposite-of-rest.md +++ b/www/essays/how-did-rest-come-to-mean-the-opposite-of-rest.md @@ -152,13 +152,13 @@ goes on to say: > choices that are present in the received representations or implied by the user’s manipulation of those representations. So, in a RESTful system, you should be able to enter the system through a single URL and, from that point on, all navigation -and actions take do within the system should be entirely provided through self-describing hypermedia: through links and +and actions taken within the system should be entirely provided through self-describing hypermedia: through links and forms in HTML, for example. Beyond the entry point, in a proper RESTful system, the API client shouldn't need any additional information about your API. -This is the core source of incredible flexibility of RESTful systems: since all responses are self describing and +This is the source of the incredible flexibility of RESTful systems: since all responses are self describing and encode all the currently available actions available there is no need to worry about, for example, versioning your API! -In fact, you don't even need to document it! All end points are provided through self-contained hypermedia controls. +In fact, you don't even need to document it! If things change, the hypermedia responses change, and that's it.