diff --git a/src/pages/contributing/code.mdx b/src/pages/contributing/code.mdx
index ac2adb7622b..4118da5dab2 100644
--- a/src/pages/contributing/code.mdx
+++ b/src/pages/contributing/code.mdx
@@ -34,7 +34,7 @@ roadmap, is open for community contribution.
 The best way to volunteer is to look through
 [existing GitHub issues](https://github.com/carbon-design-system/carbon/issues?q=is%3Aopen+is%3Aissue+label%3A%22needs%3A+community+contribution%22+)
 labeled with `needs: community contribution`. Any issue labeled with
-`needs: code contribution` is fair game! Put a comment in the issue saying you'd
+`needs: code contribution` is fair game! Put a comment in the issue saying you’d
 like to help.
 
 <Video
@@ -60,7 +60,7 @@ bug? First, be sure to look through the
 [issue backlog](https://github.com/carbon-design-system/carbon/issues) to make
 sure it is a novel idea or bug. Then, file your proposal on GitHub using the
 [issue templates](https://github.com/carbon-design-system/carbon/issues/new/choose).
-If you're willing to work on this idea yourself, be sure to let us know in your
+If you’re willing to work on this idea yourself, be sure to let us know in your
 issue! Your idea will then go through a triage process by the Carbon team.
 
 ## Step 2: Set up your environment
@@ -96,7 +96,7 @@ team and we will help you refine your issue:
 
 ## Step 4: Get feedback
 
-Most contributors work in groups of 2-3 and either set up weekly sessions or
+Most contributors work in groups of 2–3 and either set up weekly sessions or
 join [meetups](/whats-happening/meetups/#carbon-office-hours) such as the Data
 Viz Guild or Carbon Developer office hours. In these sessions, it is common to
 share work in progress and ask lots of questions. As you make progress, update