Text review, missing line break, and specify it's a path parameter

Author: RebeccaTamachiro

src/content/docs/ssl/edge-certificates/custom-certificates/troubleshooting.mdx

@@ -46,7 +46,8 @@ If you are using a Let's Encrypt certificate uploaded by yourself as a custom ce
 **Root cause**
 
 The certificate you are trying to upload is invalid. For example, there might be extra lines, or the BEGIN/END text is not correct, or extra characters are added following a copy/paste.
-In the case of an update with the [PATCH API call](/api/resources/custom_certificates/methods/edit/) it can mean the `{custom_certificate_id}` is invalid.
+
+In the case of an update with the [PATCH API call](/api/resources/custom_certificates/methods/edit/), it can mean the path parameter `{custom_certificate_id}` is invalid.
 
 **Solution**
 
@@ -56,7 +57,7 @@ Carefully check the content of the certificate. You may use `openssl` to check a
 openssl x509 -in certificate.crt -noout -text
 ```
 
-Carefully check the `{custom_certificate_id}` parameter when using the API. You can confirm the certificate ID by [listing the existing custom certificates](/api/resources/custom_certificates/methods/list/) (`id` in the response).
+When using the API, carefully check the `{custom_certificate_id}` path parameter. You can confirm the certificate ID by [listing the existing custom certificates](/api/resources/custom_certificates/methods/list/) (`id` in the response).
 
 ### You have reached the maximum number of custom certificates. (Code: 1212)