Fix codec error in md (#2234)

## Changes
- replaced curly quotes by straight quotes. 

### Linked issues
curly quotes creates a codification error in windows machines.

![image](https://github.com/user-attachments/assets/cae7adfd-45c7-48c1-8038-c3ba2e42f136)

---------

Co-authored-by: Cor <[email protected]>

Author: tarikcurto

README.md

@@ -1369,7 +1369,7 @@ NO_MATCHING_DISTRIBUTION_ERROR.
 
 **Solution:** Version 0.24.0 of UCX supports workspace with no internet
 access. Please upgrade UCX and rerun the installation. Reply *yes* to
-the question “Does the given workspace block Internet access?” asked
+the question "Does the given workspace block Internet access?" asked
 during installation. It will then upload all necessary dependencies to
 the workspace. Also, please note that UCX uses both UC and non-UC
 enabled clusters. If you have different proxy settings for each, then
@@ -1423,13 +1423,13 @@ Admin privileges required for commands:
 
 **Python:** UCX needs Python version 3.10 or later.
 
-**Solution:** Check the current version using “python --version”. If the
+**Solution:** Check the current version using `python --version`. If the
 version is lower than 3.10, upgrade the local Python version to 3.10 or
 higher.
 
 **Databricks CLI:** Databricks CLI v0.213 or higher is needed.
 
-**Solution:** Check the current version with “databricks --version”. For
+**Solution:** Check the current version with `databricks --version`. For
 lower versions of CLI,
 [<u>update</u>](https://docs.databricks.com/en/dev-tools/cli/install.html#update)
 the Databricks CLI on the local machine.
@@ -1443,8 +1443,8 @@ UCX version.
 **Solution:** Upgrade UCX, and rerun the assessment job before running
 the migration workflows. For some reason, if you want to install a
 specific version of UCX, you can do it using the command
-“databricks labs install ucx@\<version\>”, for example,
-“databricks labs install [email protected]”.
+`databricks labs install ucx@\<version\>`, for example,
+`databricks labs install [email protected]`.
 
 [[back to top](#databricks-labs-ucx)]
 
@@ -1459,8 +1459,8 @@ profiles, and tokens.
 **Account Level:** Not only workspace, but account level authentication
 is also needed for installing UCX. If you do not have an account
 configured in .databrickscfg, you will get an error message
-“.databrickscfg does not contain account profiles; please create one
-first”.
+".databrickscfg does not contain account profiles; please create one
+first".
 
 **Solution:** To authenticate with a Databricks account, consider using
 one of the following authentication types: [<u>OAuth machine-to-machine
@@ -1482,17 +1482,17 @@ workspace.
 
 **Solution:** The Databricks CLI provides an option to select the
 [<u>profile</u>](https://docs.databricks.com/en/dev-tools/cli/profiles.html)
-using “*--profile \<profile_name\>*” or “*-p \<profile_name\>*”. You can
+using `--profile \<profile_name\>` or `-p \<profile_name\>`. You can
 test that the correct workspace is getting selected by running any
-Databricks CLI command. For example, you can run “*databricks clusters
-list -p prod*” and check that the Prod clusters are being returned. Once
+Databricks CLI command. For example, you can run `databricks clusters
+list -p prod` and check that the Prod clusters are being returned. Once
 the profile is verified, you can run UCX install for that specific
-profile: “*databricks labs install ucx -p prod*”.
+profile: `databricks labs install ucx -p prod`.
 
 **Account Level:** Multiple account level profiles are set in the
 .databrickscfg file.
 
-**Solution:** The installation command “*databricks labs install ucx*”
+**Solution:** The installation command `databricks labs install ucx`
 will provide an option to select one account profile.
 
 [[back to top](#databricks-labs-ucx)]
@@ -1529,7 +1529,7 @@ under Data Access Configuration of SQL Warehouse Admin Settings.
 
 ### Verify the Installation
 
-Once the UCX command “*databricks labs install ucx*” has completed
+Once the UCX command `databricks labs install ucx` has completed
 successfully, the installation can be verified with the following steps:
 
 1.  Go to the Databricks Catalog Explorer and check if a new schema for

docs/assessment.md

@@ -853,7 +853,7 @@ The `.sequenceFile` pattern was found. Use "Assigned" access mode compute or mak
 ### AF313.18 - SparkContext ( `.setJobGroup` )
 
 The `.setJobGroup` pattern was found.
-`spark.addTag()` can attach a tag, and `getTags()` and `interruptTag(tag)` can be used to act upon the presence/absence of a tag. These APIs only work with Spark Connect (Shared Compute Mode) and will not work in “Assigned” access mode.
+`spark.addTag()` can attach a tag, and `getTags()` and `interruptTag(tag)` can be used to act upon the presence/absence of a tag. These APIs only work with Spark Connect (Shared Compute Mode) and will not work in "Assigned" access mode.
 
 [[back to top](#migration-assessment-report)]
 

src/databricks/labs/ucx/queries/assessment/estimates/00_0_metastore_assignment.md

@@ -18,4 +18,4 @@ If you haven't created a metastore yet, follow the docs below to attach your wor
 If any incompatible submit runs has been detected, follow the steps highlighted below:
 
 1. Find out the incompatible jobs in your local orchestrator based on the object_id identified by UCX
-2. Change the job configuration to include the following in the ClusterInfo:   “data_security_mode”: “NONE”
+2. Change the job configuration to include the following in the ClusterInfo:   "data_security_mode": "NON"

src/databricks/labs/ucx/source_code/path_lookup.py

@@ -35,7 +35,7 @@ def change_directory(self, new_working_directory: Path) -> PathLookup:
     def resolve(self, path: Path) -> Path | None:
         try:
             if path.is_absolute() and path.exists():
-                # eliminate “..” components
+                # eliminate ".." components
                 return path.resolve()
         except PermissionError:
             logger.warning(f"Permission denied to access {path}")
@@ -55,7 +55,7 @@ def _resolve_in_library_root(self, library_root: Path, path: Path) -> Path | Non
             return None
         absolute_path = library_root / path
         if absolute_path.exists():
-            return absolute_path.resolve()  # eliminate “..” components
+            return absolute_path.resolve()  # eliminate ".." components
         return self._resolve_egg_in_library_root(library_root, path)
 
     def _resolve_egg_in_library_root(self, library: Path, path: Path) -> Path | None:
@@ -64,7 +64,7 @@ def _resolve_egg_in_library_root(self, library: Path, path: Path) -> Path | None
                 continue
             absolute_path = child / path
             if absolute_path.exists():
-                return absolute_path.resolve()  # eliminate “..” components
+                return absolute_path.resolve()  # eliminate ".." components
         return None
 
     @staticmethod

tests/unit/source_code/samples/01_HL7Streaming.scala

@@ -216,6 +216,6 @@ for (s <- spark.streams.active) {
 
 // MAGIC %md
 // MAGIC ## Disclaimers
-// MAGIC Databricks Inc. (“Databricks”) does not dispense medical, diagnosis, or treatment advice. This Solution Accelerator (“tool”) is for informational purposes only and may not be used as a substitute for professional medical advice, treatment, or diagnosis. This tool may not be used within Databricks to process Protected Health Information (“PHI”) as defined in the Health Insurance Portability and Accountability Act of 1996, unless you have executed with Databricks a contract that allows for processing PHI, an accompanying Business Associate Agreement (BAA), and are running this notebook within a HIPAA Account. Please note that if you run this notebook within Azure Databricks, your contract with Microsoft applies.
+// MAGIC Databricks Inc. ("Databricks") does not dispense medical, diagnosis, or treatment advice. This Solution Accelerator ("tool") is for informational purposes only and may not be used as a substitute for professional medical advice, treatment, or diagnosis. This tool may not be used within Databricks to process Protected Health Information ("PHI") as defined in the Health Insurance Portability and Accountability Act of 1996, unless you have executed with Databricks a contract that allows for processing PHI, an accompanying Business Associate Agreement (BAA), and are running this notebook within a HIPAA Account. Please note that if you run this notebook within Azure Databricks, your contract with Microsoft applies.
 // MAGIC 
 // MAGIC All names have been synthetically generated, and do not map back to any actual persons or locations