diff --git a/_docs/documenting_api_endpoints/docapis_resource_endpoints.md b/_docs/documenting_api_endpoints/docapis_resource_endpoints.md
index d29daa4d..58d2dea9 100644
--- a/_docs/documenting_api_endpoints/docapis_resource_endpoints.md
+++ b/_docs/documenting_api_endpoints/docapis_resource_endpoints.md
@@ -90,7 +90,7 @@ Sometimes the method is referred to as the "verb." GET, PUT, POST, PATCH, and DE
 
 When you describe the endpoint, you list the end path only (hence the term "*end* point"). The full path that contains both the base path and the endpoint is often called a resource URL.
 
-In our sample API scenario, the endpoint is just `/surfreport/{beachId}`. You don't have to list the full resource URL every time (which would be `https://api.openweathermap.org/surfreport{beachId}`). Including the full resource URL would distract users from focusing on the path that matters. In your user guide, you usually explain the full resource URL, along with the required [authorization](docapis_more_about_authorization.html), in an introductory section (such as the [Getting started tutorial](docapis_doc_getting_started_section.html)).
+In our sample API scenario, the endpoint is just `/surfreport/{beachId}`. You don't have to list the full resource URL every time (which would be `https://api.openweathermap.org/surfreport/{beachId}`). Including the full resource URL would distract users from focusing on the path that matters. In your user guide, you usually explain the full resource URL, along with the required [authorization](docapis_more_about_authorization.html), in an introductory section (such as the [Getting started tutorial](docapis_doc_getting_started_section.html)).
 
 ## How to group multiple endpoints for the same resource