style: remove fancy quotes

---
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:
  - task: lint_filenames
    status: passed
  - task: lint_editorconfig
    status: passed
  - task: lint_markdown
    status: passed
  - task: lint_package_json
    status: na
  - task: lint_repl_help
    status: na
  - task: lint_javascript_src
    status: na
  - task: lint_javascript_cli
    status: na
  - task: lint_javascript_examples
    status: na
  - task: lint_javascript_tests
    status: na
  - task: lint_javascript_benchmarks
    status: na
  - task: lint_python
    status: na
  - task: lint_r
    status: na
  - task: lint_c_src
    status: na
  - task: lint_c_examples
    status: na
  - task: lint_c_benchmarks
    status: na
  - task: lint_c_tests_fixtures
    status: na
  - task: lint_shell
    status: na
  - task: lint_typescript_declarations
    status: na
  - task: lint_typescript_tests
    status: na
  - task: lint_license_headers
    status: passed
---

Author: anandkaranubc

docs/contributing/FAQ.md

@@ -46,7 +46,7 @@ limitations under the License.
 
 ## Introduction
 
-We appreciate your interest in contributing to stdlib! Below, we’ve compiled answers to some frequently asked questions (FAQs) from first-time contributors. If you’re new to the project or encounter any challenges, this guide is a great place to start.
+We appreciate your interest in contributing to stdlib! Below, we've compiled answers to some frequently asked questions (FAQs) from first-time contributors. If you're new to the project or encounter any challenges, this guide is a great place to start.
 
 <a name="first-time-contributor"></a>
 

docs/contributing/git_cheatsheet.md

@@ -86,7 +86,7 @@ git checkout -b feature/my-new-feature
 
 ## Changes
 
-Now comes the fun part of actually writing code! After making your changes, it's always good to check what’s modified:
+Now comes the fun part of actually writing code! After making your changes, it's always good to check what's modified:
 
 <!-- run-disable -->
 
@@ -157,7 +157,7 @@ Once your branch is ready, you need to push your **local** changes to your forke
 git push
 ```
 
-If this is the first time you’re pushing the branch, [Git][git] may prompt you to set an [upstream][git-remotes] branch. You can do this manually by running:
+If this is the first time you're pushing the branch, [Git][git] may prompt you to set an [upstream][git-remotes] branch. You can do this manually by running:
 
 <!-- run-disable -->
 
@@ -307,7 +307,7 @@ Use **Rebase** if:
 
 Use **Merge** if:
 
--   You want a safer approach that doesn’t rewrite history.
+-   You want a safer approach that doesn't rewrite history.
 -   You are unsure about rebase or are collaborating on the branch.
 
 > **When in doubt, use merge.** It is safer and avoids potential conflicts caused by rewriting history. If you use the GitHub UI to update your branches, it also performs a merge.

docs/contributing/setting_up_a_devcontainer.md

@@ -42,7 +42,7 @@ Setting up the stdlib dev container **requires** the following prerequisites:
 
 ### Download
 
-To acquire the source code, first navigate to the parent directory where you want to place the project’s [Git][git] repository.
+To acquire the source code, first navigate to the parent directory where you want to place the project's [Git][git] repository.
 
 <!-- run-disable -->