updating repo URLs

Author: toumorokoshi

pages/general/adopting.md

@@ -13,13 +13,11 @@ Having an AEP-compliant API also means benefitting from the AEP ecosystem of
 tooling, such as:
 
 - Linters and validators to ensure adherence to the AEP design specification
-  [proto]()/[openapi]()
+  ([proto](https://github.com/aep-dev/api-linter)/[openapi](https://github.com/aep-dev/aep-openapi-linter))
 - A dynamic command line interface generator that make it easier to work with
   APIs ([aepcli](https://github.com/aep-dev/aepcli))
 - Client-side and server-side code generators
   ([aepc](https://github.com/aep-dev/aepc))
-- A Terraform provider
-  ([terraform-provider-aep](https://github.com/aep-dev/terraform-provider-aep))
 - ... and more! Please start a
   [discussion](https://github.com/aep-dev/aep.dev/discussions) if there is
   something you wish to see, validate, or prioritize.