Consistently use the same apostrophe in these docs.

llvm/docs/CodeOfConduct.rst

@@ -112,7 +112,7 @@ immediate attention, you can also reach out to any of the event organizers or
 staff. Event organizers and staff will be prepared to handle the incident and
 able to help. If you cannot find one of the organizers, the venue staff can
 locate one for you. We will also post detailed contact information for specific
-events as part of each events’ information. In person reports will still be
+events as part of each events' information. In person reports will still be
 kept confidential exactly as above, but also feel free to (anonymously if
 needed) email conduct@llvm.org.
 

llvm/docs/ReportingGuide.rst

@@ -5,7 +5,7 @@ LLVM CoC Incident Reporting Guide
 First of all, please do not feel like you may be a burden to us by reporting
 incidents. We consider reports an opportunity for us to act: by knowing about
 an incident, we can act on it if appropriate, and reduce continuation of
-problematic behavior.  If we don’t know, we can't learn or take any appropriate
+problematic behavior.  If we don't know, we can't learn or take any appropriate
 actions.
 
 If you are not sure the situation being reported was a :doc:`Code of
@@ -23,12 +23,12 @@ Reporting and Contact Information
   irc/discord/slack, etc) we ask that you make any reports by emailing 
   conduct@llvm.org. This is received by all members of the CoC Committee.
 
-* For LLVM Developers’ Meetings, please file a report with the on-site Code 
+* For LLVM Developers' Meetings, please file a report with the on-site Code 
   of Conduct team. Their names and contact details are listed on the event 
   webpage. You can also approach any other staff member, who can be 
   identified by special badges and often found at the registration desk, 
   to help you locate a member of the Code of Conduct team. All incidents 
-  reported in-person at a LLVM Developers’ Meeting will be emailed to the 
+  reported in-person at a LLVM Developers' Meeting will be emailed to the 
   Code of Conduct Committee. 
 
 * For meetups, please report the incident to the local meetup organizers first

llvm/docs/ResponseGuide.rst

@@ -17,7 +17,7 @@ Additional Code of Conduct Response Teams
 In-person events will have an additional response team to immediately respond
 to an incident. For example:
 
-* Each LLVM Developers’ Meeting has a Code of Conduct response team.
+* Each LLVM Developers' Meeting has a Code of Conduct response team.
 * For LLVM meetups, the local organizers will be the first point of contact.
 * Any other event funded by the LLVM Foundation or listed on the LLVM website,
   will have a code of conduct response team or point of contact for CoC 
@@ -265,7 +265,7 @@ enforcement decision has been made.
 
 In the event of a temporary suspension or ban, the appropriate people must be
 notified of the ban in order to restrict access to infrastructure or events.
-These individuals will only be notified of the person’s name and the
+These individuals will only be notified of the person's name and the
 restrictions imposed. They will be under a confidentiality clause and not
 allowed to respond to questions regarding the ban and should direct all
 questions to the CoC committee. 
@@ -279,7 +279,7 @@ Lack of transparency in the outcomes of our Code of Conduct incidents leaves
 our community without an understanding of how or if the organizers worked to
 resolve incidents. The CoC committee should aim to publish transparency
 reports, if reports are received, after major events (such as the LLVM
-Developers’ meetings) and on the following dates: Jan 15, April 15, July 15,
+Developers' meetings) and on the following dates: Jan 15, April 15, July 15,
 Oct 15. 
 
 A transparency report consists of 2 parts: