fix build errors

Author: JimDaly

powerapps-docs/developer/common-data-service/custom-api.md

@@ -74,7 +74,7 @@ If you do not set the **Plugin Type** (`PluginTypeId`)  to specify main operatio
 **Known Issues**:
 
 - [The Is Private field is not included in the Custom API form](#the-is-private-field-is-not-included-in-the-custom-api-form)
-- [Custom API functions cannot use Entity or EntityCollection Request Parameters or Response Properties](#custom-api-functions-cannot-use-entity-or-entitycollection-request-parameters-or-response-properties)
+- [Custom API functions cannot use Entity or EntityCollection Request Parameters](#custom-api-functions-cannot-use-entity-or-entitycollection-request-parameters)
 
 ### CustomAPIRequestParameter entity attributes
 

powerapps-docs/developer/common-data-service/workflow-custom-actions.md

@@ -18,7 +18,7 @@ search.app:
 
 # Use Workflow Custom Actions with code
 
-Workflow Custom Actions, also known as simply *Custom Actions*, are one of two ways to create custom messages for the Common Data service. The other is a preview feature called *Custom APIs*. More information: [Create and use Custom APIs](custom-api).
+Workflow Custom Actions, also known as simply *Custom Actions*, are one of two ways to create custom messages for the Common Data service. The other is a preview feature called *Custom APIs*. More information: [Create and use Custom APIs](custom-api.md).
 
 Both of these capabilities allow for creating new messages that can be called from web services. Workflow Custom Actions will continue to provide a no-code way to declaratively define synchronous business logic. Custom actions have always been synchronous 'real-time' workflows and therefore not suitable to be converted to use Power Automate.