Skip to content

Commit bce31ff

Browse files
committed
Azure Container offers certification
1 parent 51156fe commit bce31ff

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/marketplace/azure-container-certification-faq.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ metadata:
1010
ms.date: 09/27/2021
1111
title: Troubleshoot container certification
1212
summary: |
13-
When you publish your container products to Azure Marketplace, the Azure team validates it to ensure that it's secure. If your container products fails any of the tests, it won't be published. You'll receive an error message that describes the issue.
13+
When you publish your container products to Azure Marketplace, the Azure team validates it to ensure that it's secure. If your container products fail any of the tests, it won't be published. You'll receive an error message that describes the issue.
1414
1515
This article explains common error messages during container publishing, along with related solutions.
1616
@@ -25,14 +25,14 @@ sections:
2525
Vulnerability failure
2626
answer: |
2727
A vulnerability is an exploitable risk and/or an unsecured entry points that can be used by malicious actors for nefarious actions.
28-
If you are planning to publish container products, you should scan your product for vulnerability and fix them before publishing the container product.
28+
If you're planning to publish container products, you should scan your product for vulnerability and fix them before publishing the container product.
2929
If your existing container products have vulnerabilities in them, you should deprecate/hide the affected offer and republish after fixing the vulnerabilities.
3030
3131
- question: |
3232
Malware failure
3333
answer: |
3434
A malware, or malicious software, is a file or program that is designed to be harmful to computer, network or servers.
35-
If you are planning to publish container products, you should scan your product for malware, identify all files which contain malware and remove them before publishing the container product.
35+
If you're planning to publish container products, you should scan your product for malware, identify all files that contain malware and remove them before publishing the container product.
3636
If your existing container products have malware, you should deprecate/hide the affected offers and republish the patched product.
3737
3838

0 commit comments

Comments
 (0)