https://docs.microsoft.com/ja-jp/surface/microsoft-surface-data-eraser
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@officedocsbot assign @OfficeGlobal
@OfficeGlobal - Kindly assist with this Translation (Localization) issue. Thank you.
@officedocsbot assign @mypil
@dongmicro - Can you assist with this Translation (Localization) issue?
Thank you.
@dongmicro - I would like to follow up on this. Do you have any updates? Thanks.
cc: @AndreaBarr
@officedocsbot add label localization
@dongmicro - I would like to follow up on this. Can you please assist with this Translation (Localization) issue? Thanks.
Under investigation.
Oh. I think I can see why this is happening. This is about the image text *Figure 2. USB thumb drive selection* (under image 2 in the section How to create a Microsoft Surface Data Eraser USB stick.
Right above the image, there is a note message. followed by the image and the affected figure text:
Select the USB drive of your choice from the USB Thumb Drive Selection page as shown in Figure 2, and then click Start to begin the USB creation process. The drive you select will be formatted and any existing data on this drive will be lost.
[!NOTE]
If the Start button is disabled, check that your removable drive has a total capacity of at least 4 GB.

*Figure 2. USB thumb drive selection*
To me, it looks like the Github indentation, along with the asterisks used to format the text as italics, puts the image text in a code block instead of showing it as formatted text, hence making the asterisks show up on the Github page. This looks like the note above the image, along with the following indentation, makes this happen instead of showing the text as regular formatted text.
The weird thing to me is that the format issue does not show up on the docs.microsoft.com page, neither the Japanese version nor the en-us version of the page, neither in MS Edge nor in Chrome.
I admit I am a little bit confused now, seeing that I can only reproduce it using Github, not the docs.microsoft.com page.
@Maruktruk @dongmicro - Any updates on this?
Looking forward to hear from you, @Maruktruk & @dongmicro.
@officedocsbot unassign @OfficeGlobal
@officedocsbot assign @dongmicro
Similar: #3394 #3453 #3452 #3451
@officedocsbot unassign @mypil
@officedocsbot assign @e0i
@officedocsbot assign @MollyMalone
@officedocsbot unassign @MollyMalone
@officedocsbot assign @TinaMcN
@e0i : Looking back at the pages now, this specific issue seems to be resolved, both for the Japanese and Github pages:
May I ask for you and @hyoshioka0128 to confirm that this is the case, testing several of your browsers as well?
If this issue really is solved, would you like to collect the remaining open linked issues in a different issue page?
@officedocsbot unassign @dongmicro
@officedocsbot close
This issue appears to be fixed.
@TinaMcN Thank you. Would you confirm that associated group of issues have also been fixed?
Manually run through associated issues and closed the ones that have been fixed. Thanks.
@e0i thanks so much for doing that - much appreciated 👍
Most helpful comment
@officedocsbot close
This issue appears to be fixed.