added "using instrumentationo libraries" for cpp

content/en/docs/languages/cpp/library.md

@@ -15,7 +15,7 @@ instrument your app using OpenTelemetry, you might want to avoid spending additi
 logs, and metrics to the third-party libraries and frameworks you use.
 
 Many libraries and frameworks already support OpenTelemetry or are supported through OpenTelemetry
-[instrumentation](/docs/concepts/instrumentation/libraries/),
+[instrumentation](https://opentelemetry.io/docs/concepts/instrumentation/libraries/),
 so that they can generate telemetry you can export to an observability back end.
 
 If you are instrumenting an app or service that use third-party libraries or frameworks, follow these instructions to 
@@ -35,7 +35,7 @@ library to learn more.
 
 
 If a library doesn't include OpenTelemetry support, you can use
-[instrumentation libraries](/docs/specs/otel/glossary/#instrumentation-library)
+[instrumentation libraries](https://opentelemetry.io/docs/specs/otel/glossary/#instrumentation-library)
 to generate telemetry data for a library or framework.
 
 For example,
@@ -56,9 +56,9 @@ A full list of instrumentation libraries available can be found in the [openTele
 ## Next steps
 
 After you've set up instrumentation libraries, you might want to add
-[additional instrumentation](/docs/languages/php/instrumentation) to collect
+[additional instrumentation](https://opentelemetry.io/docs/languages/cpp/instrumentation/) to collect
 custom telemetry data.
 
 You might also want to configure an appropriate exporter to
-[export your telemetry data](/docs/languages/cpp/exporters) to one or more
+[export your telemetry data]( https://opentelemetry.io/docs/languages/cpp/exporters/) to one or more
 telemetry backends.