Fix broken links in README.md (#1747)

Author: garysassano

collector/README.md

@@ -27,7 +27,7 @@ Once this build-tag is present, you need provide additional build-tags to includ
 - `lambdacomponents.processor.all` includes all available processors
 - `lambdacomponents.receiver.all` includes all available receivers
 
-Each available component can also be included explicitly by using its specific build-tag. For a full-list of available components, have a look into the [lambdacomponents](./collector/lambdacomponents) package.
+Each available component can also be included explicitly by using its specific build-tag. For a full-list of available components, have a look into the [lambdacomponents](./lambdacomponents) package.
 
 As an example, the full command to publish OpenTelemetry Collector Lambda layer in your AWS account and get its ARN including the following components:
 - All receivers
@@ -42,10 +42,10 @@ cd collector && BUILDTAGS="lambdacomponents.custom,lambdacomponents.receiver.all
 ```
 
 ### Adding additional options
-To add more options for a customized build, you can add your desired component to the [lambdacomponents](./collector/lambdacomponents) package.
+To add more options for a customized build, you can add your desired component to the [lambdacomponents](./lambdacomponents) package.
 Make sure to always restrict your addition using the appropriate build-tags.
 
-For example, if you want to add the extension `foo`, the file providing this extension should be located in the [extension](./collector/lambdacomponents/extension) directory have the following build restriction:
+For example, if you want to add the extension `foo`, the file providing this extension should be located in the [extension](./lambdacomponents/extension) directory have the following build restriction:
 ```
 //go:build lambdacomponents.custom && (lambdacomponents.all || lambdacomponents.extension.all || lambdacomponents.extension.foo)
 ```