Update prevent_spam_flag.md

Few links update and typos

Author: henikaraa

articles/communication-services/concepts/telephony/prevent_spam_flag.md

@@ -22,17 +22,17 @@ When phone numbers are flagged as spam, it can severely impact the ability of bu
 ## Requirements and Best Practices for Voice Communications
 
 1. **Monitor Call Patterns:** Regularly monitor call patterns to identify any unusual activity that may trigger spam filters. Avoid making a high volume of calls in a short period.
-2. **Use Caller ID:** Ensure that the customer’s caller ID is correctly set up and displays accurate information. This helps recipients recognize the caller and reduces the likelihood of being reported as spam (You can leverage the Azure Communication process for CNAM setup detailed [here](https://learn.microsoft.com/azure/communication-services/concepts/telephony/how-to-manage-your-calling-identity)).
+2. **Use Caller ID:** Ensure that the customer’s caller ID is correctly set up and displays accurate information. This helps recipients recognize the caller and reduces the likelihood of being reported as spam (You can leverage the Azure Communication process for CNAM setup detailed [here](../telephony/how-to-manage-your-calling-identity.md)).
 3. **Obtain Consent:** Always obtain consent from recipients before making calls. This can be done through opt-in mechanisms where customers explicitly agree to receive calls from the customer’s business.
 4. **Provide Opt-Out Options:** Offer recipients an easy way to opt-out of receiving calls. This can be done through automated systems or customer service representatives.
-5. **Maintain a Clean Contact List:** Regularly update and clean customer’s contact list to remove inactive or incorrect numbers. This reduces the chances of calling numbers that may report customer’s calls as spam. Customers can leverage the Azure Communication Services Number Lookup API to help customers with this (more details [here](https://learn.microsoft.com/azure/communication-services/concepts/numbers/number-lookup-concept)).
+5. **Maintain a Clean Contact List:** Regularly update and clean customer’s contact list to remove inactive or incorrect numbers. This reduces the chances of calling numbers that may report customer’s calls as spam. Customers can leverage the Azure Communication Services Number Lookup API to help customers with that (more details [here](../../quickstarts/telephony/number-lookup.md)).
 
 ## Prohibited uses of Communications Services
 
 The following activities are prohibited:
 1.	Using Communications Services in any manner that may expose Microsoft or any of its personnel to criminal or civil liability;
 2.	Re-selling Calling Plan and Audio Conferencing subscription minutes;
-3.	Placing calls to or from Microsoft issued telephone numbers (whether singly, sequentially, or automatically) to generate income for yourself or others as a result of placing the call, other than for Customer’s business communications; and
+3.	Placing calls to or from Microsoft issued telephone numbers (whether singly, sequentially, or automatically) to generate income for yourself or others as a result of placing the call, other than for Customer’s business communications;
 4.	Placing calls in unusual calling patterns inconsistent with normal, individual subscription use, for example, placing regular calls of short durations or calls to multiple numbers in a short period of time.
 5.	Using Communications Services in violation of any applicable laws or regulations of any jurisdiction, including, but not limited to, (a) privacy or data protection laws or regulations; (b) laws requiring consent of participants to receive calls or text messages; (c) laws governing the recording or monitoring of telephone calls; (d) laws and regulations that prohibit unsolicited, unwanted or harassing communications; or (e) anti-spam laws such as the U.S. CAN SPAM Act of 2003 and the Do-Not-Call Implementation Act.
 
@@ -43,7 +43,7 @@ For the full list of applicable Azure Communication Services Terms, you can refe
 The [Free Caller Registry](https://www.freecallerregistry.com/fcr/) (FCR) serves as a system for organizations that conduct outbound calls to secure approval for their phone numbers, ensuring they are not incorrectly tagged as “Spam Likely” or “Scam” by mobile service providers. This initiative is backed by leading US vendors (TNS, FirstOrion and Hiya) who develop mechanisms to label incoming calls with a “Spam Likely” indicator. The registry holds significant importance for entities dependent on outbound calls for their business activities, as it helps to prevent their calls from being intercepted or wrongly marked as spam by carriers or external services. We recommend that customers initiate the process of phone number registration to mitigate this risk.
 
 In order to request registration for an Azure Communication Services number, customers will need to work through the following steps:
-1. Visit Free Caller Registry and click on “*Register here*”
+1. Visit [Free Caller Registry](https://www.freecallerregistry.com/fcr/) and click on “*Register here*”
 2. Complete the form with all the details about numbers that customers own and will be using for PSTN Outbound calls, company’s details as well as expected volume and justification for the request.
 3. Once a customer’s work email has been verified, he can submit his request.