“ should be "

Full width turn half-width character

Signed-off-by: YuPengZTE <yu.peng36@zte.com.cn>

docs/admin/b2d_volume_resize.md

@@ -9,7 +9,7 @@ parent = "smn_win_osx"
 +++
 <![end-metadata]-->
 
-# Getting “no space left on device” errors with Boot2Docker?
+# Getting "no space left on device" errors with Boot2Docker?
 
 If you're using Boot2Docker with a large number of images, or the images you're
 working with are very large, your pulls might start failing with "no space left

docs/admin/runmetrics.md

@@ -65,8 +65,8 @@ known to the system, the hierarchy they belong to, and how many groups they cont
 
 You can also look at `/proc/<pid>/cgroup` to see which control groups a process
 belongs to. The control group will be shown as a path relative to the root of
-the hierarchy mountpoint; e.g., `/` means “this process has not been assigned into
-a particular group”, while `/lxc/pumpkin` means that the process is likely to be
+the hierarchy mountpoint; e.g., `/` means "this process has not been assigned into
+a particular group", while `/lxc/pumpkin` means that the process is likely to be
 a member of a container named `pumpkin`.
 
 ## Finding the cgroup for a given container
@@ -279,7 +279,7 @@ program (present in the host system) within any network namespace
 visible to the current process. This means that your host will be able
 to enter the network namespace of your containers, but your containers
 won't be able to access the host, nor their sibling containers.
-Containers will be able to “see” and affect their sub-containers,
+Containers will be able to "see" and affect their sub-containers,
 though.
 
 The exact format of the command is: