Update location_component_interface.adoc

Fix markdown typo

Author: spencer-lunarg

chapters/location_component_interface.adoc

@@ -9,9 +9,9 @@ ifndef::images[:images: images/]
 
 This chapter is an overview of the link:https://docs.vulkan.org/spec/latest/chapters/interfaces.html#interfaces-iointerfaces-locations[Location and Component Assignment] chapter to help give examples, especially around some of the more extreme edge cases.
 
-The simplest way to think about a `Location` is that it is made up of four 32-bit `Components`.
+The simplest way to think about a `Location` is that it is made up of four 32-bit `Component`.
 This means a `vec4`/`float4`/`uvec4`/etc will fit perfectly in a single `Location`.
-Multiple variables can be packed into the same `Location` if their `Components` do not overlap.
+Multiple variables can be packed into the same `Location` if their `Componens` do not overlap.
 
 Locations are used for both the `Input` and `Output` to interface between shaders stages when possible.
 
@@ -20,7 +20,7 @@ Locations are used for both the `Input` and `Output` to interface between shader
 For most people, this chapter is much deeper into edge cases compared who developers generally use the `Location` interface. For those developers, the simple advise to take away is:
 
 1. Use less `Location` if possible.
-2. If you need many `Location`s, make sure you are link:https://docs.vulkan.org/spec/latest/chapters/interfaces.html#interfaces-iointerfaces-limits[under the limits].
+2. If you need many `Location`, make sure you are link:https://docs.vulkan.org/spec/latest/chapters/interfaces.html#interfaces-iointerfaces-limits[under the limits].
 
 == Basic Example