Update how-to-insert-a-picture-into-a-word-processing-document.md

[p-kaczynski]

The current code contains a bug that makes the document not open in MS Word. This single error (https instead of http in URI) causes the document to be unopenable in any tested Word product (Word for Office 365 Win/macOS/iOS, MS Word Professional 2016).

Interestingly it does open fine in LibreOffice and others.

[opbld32]

Docs Build status updates of commit 066149e:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
docs/docfx.json	❌Error		Details

docs/docfx.json

• Line 55, Column 0: [Error-json-syntax-error] Unexpected end of content while loading JObject.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[sdudnic]

the problem still present here https://docs.microsoft.com/en-us/office/open-xml/how-to-insert-a-picture-into-a-word-processing-document

[tomjebo]

@lindalu-MSFT This PR appears to have been merged but the content is still saying "https". It should be "http". Does it take a while to publish the changes on the live content?

[lindalu-MSFT]

@tomjebo Thanks for letting me know. It appears that the PR was merged to master but then never published. I just merged master to live, so the change should be on the live content shortly. Usually takes less than 10 min or so. Check back later, and if the problem still persists, I suggest creating a NEW PR and we'll try again. Thanks, linda

[sdudnic]

as already commented in another thread, not fixed for VB.NET

[tomjebo]

@sdudnic you should submit a PR with the fixes for the other 3 instances of this error.

[sdudnic]

What is that PR... Suppose Pull or Push Request? Other 3 instances?