commit 65bc16c13ffd3b7720c84d1f41c5a84b77db8dcc
parent a6b4ede1304f42455fbffb5c2daf1c5965aa3876
Author: Joakim <52826317+ImJoakim@users.noreply.github.com>
Date: Tue, 20 Jul 2021 01:59:24 +0200
Fixed links and spacing (#1314)
* Fixed links in repository.md
* Fixed link in manifest.md
* Fixed links in windows-package-manager-policies.md
* Fixed links and spelling in winget-validation.md
* Fixed links in export.md
* Fixed link in features.md
* Fixed link in import.md
* Fixed links in index.md
* Fixed link in list.md
* Fixed link in uninstall.md
* Fixed links in upgrade.md
* Fixed link in validate.md
* Removed en-us
Diffstat:
12 files changed, 39 insertions(+), 39 deletions(-)
diff --git a/doc/windows/package-manager/package/manifest.md b/doc/windows/package-manager/package/manifest.md
@@ -193,7 +193,7 @@ You can often figure out what silent `Switches` are available for an installer b
| Installer | Command | Documentation |
| :--- | :-- | :--- |
-| MSI | `/q` | [MSI Command-Line Options](/windows/win32/msi/command-line-options) |
+| MSI | `/q` | [MSI Command-Line Options](https://docs.microsoft.com/windows/win32/msi/command-line-options) |
| InstallShield | `/s` | [InstallShield Command-Line Parameters](https://docs.flexera.com/installshield19helplib/helplibrary/IHelpSetup_EXECmdLine.htm) |
| Inno Setup | `/SILENT or /VERYSILENT` | [Inno Setup documentation](https://jrsoftware.org/ishelp/) |
| Nullsoft | `/S` | [Nullsoft Silent Installers/Uninstallers](https://nsis.sourceforge.io/Docs/Chapter4.html#silent) |
diff --git a/doc/windows/package-manager/package/repository.md b/doc/windows/package-manager/package/repository.md
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
After you create a [package manifest](manifest.md) that describes your application, you're ready to submit your manifest to the Windows Package Manager repository. This a public-facing repository that contains a collection of manifests that the **winget** tool can access. To submit your manifest, you'll upload it to the open source [https://github.com/microsoft/winget-pkgs](https://github.com/microsoft/winget-pkgs) repository on GitHub.
-After you submit a **pull request** to add a new manifest to the GitHub repository, an automated process will validate your manifest file and check to make sure the package complies with the [Windows Package Manager polices](.\windows-package-manager-policies.md) and is not known to be malicious. If this validation is successful, your package will be added to the public-facing Windows Package Manager repository so it can be discovered by the **winget** client tool. Note the distinction between the manifests in the open source GitHub repository and the public-facing Windows Package Manager repository.
+After you submit a **pull request** to add a new manifest to the GitHub repository, an automated process will validate your manifest file and check to make sure the package complies with the [Windows Package Manager polices](windows-package-manager-policies.md) and is not known to be malicious. If this validation is successful, your package will be added to the public-facing Windows Package Manager repository so it can be discovered by the **winget** client tool. Note the distinction between the manifests in the open source GitHub repository and the public-facing Windows Package Manager repository.
> [!IMPORTANT]
> Microsoft reserves the right to refuse a submission for any reason.
@@ -25,7 +25,7 @@ There are currently no known third party repositories. Microsoft is working with
When you submit a manifest to the [https://github.com/microsoft/winget-pkgs](https://github.com/microsoft/winget-pkgs) repository on GitHub, your manifest will be automatically validated and evaluated for the safety of the Windows ecosystem. Manifests may also be reviewed manually.
-For information on the validation process, see [Windows Package Manager validation](.\winget-validation.md)
+For information on the validation process, see [Windows Package Manager validation](winget-validation.md)
## How to submit your manifest
@@ -33,7 +33,7 @@ To submit a manifest to the repository, follow these steps.
### Step 1: Validate your manifest
-The **winget** tool provides the [validate](..\winget\validate.md) command to confirm that you have created your manifest correctly. To validate your manifest, use this command.
+The **winget** tool provides the [validate](../winget/validate.md) command to confirm that you have created your manifest correctly. To validate your manifest, use this command.
```CMD
winget validate \<manifest-file>
@@ -102,8 +102,8 @@ After you push your changes, return to [https://github.com/microsoft/winget-pkgs
When you create a **pull request**, this will start an automated process that validates the manifests and verifies your **pull request**. During this process we will run tests against the installer and installed binaries to validate the submission.
-We add labels to your **pull request** so you can track its progress. For more information on labels and the process see [Windows Package Manager validation](.\winget-validation.md).
+We add labels to your **pull request** so you can track its progress. For more information on labels and the process see [Windows Package Manager validation](winget-validation.md).
Once complete, your submission will be manually reviewed by a moderator, and after it is approved, your application will be added to the Windows Package Manager catalog.
-If there is ever an error during the process, you will be notified and our labels and bot will assist you in fixing your submission. For the list of common errors, see [Windows Package Manager validation](.\winget-validation.md).
+If there is ever an error during the process, you will be notified and our labels and bot will assist you in fixing your submission. For the list of common errors, see [Windows Package Manager validation](winget-validation.md).
diff --git a/doc/windows/package-manager/package/windows-package-manager-policies.md b/doc/windows/package-manager/package/windows-package-manager-policies.md
@@ -85,7 +85,7 @@ The Product must not attempt to change or extend its described functionality thr
### 1.2.2
-The Product must not contain or enable malware as defined by the Microsoft criteria for [Unwanted and Malicious Software](/windows/security/threat-protection/intelligence/criteria).
+The Product must not contain or enable malware as defined by the Microsoft criteria for [Unwanted and Malicious Software](https://docs.microsoft.com/windows/security/threat-protection/intelligence/criteria).
### 1.2.3
@@ -276,7 +276,7 @@ User Generated Content (UGC) is content that users contribute to an app or Produ
### See also
-- [Change history for Windows Package Manager Policy History](.\windows-package-manager-policies-change-history.md)
+- [Change history for Windows Package Manager Policy History](windows-package-manager-policies-change-history.md)
- [Windows Package Manager Code of Conduct](https://github.com/microsoft/winget-pkgs/blob/master/CODE_OF_CONDUCT.md)
- [Windows Package Manager Contributing requirements](https://github.com/microsoft/winget-pkgs/blob/master/README.md)
\ No newline at end of file
diff --git a/doc/windows/package-manager/package/winget-validation.md b/doc/windows/package-manager/package/winget-validation.md
@@ -21,7 +21,7 @@ Here are some expectations for submissions:
- The installer comes directly from the publisher\'s website.
-Please see [Windows Package Manager policies](.\windows-package-manager-policies.md) for a complete list of the policies.
+Please see [Windows Package Manager policies](windows-package-manager-policies.md) for a complete list of the policies.
## Pull request labels
@@ -53,21 +53,21 @@ immediately. Some may trigger manual validation.
| **Label** | **Details** |
|--------------|-------------|
|<img width=200/>|<img width=500/>|
-| **Binary-Validation-Error** | The application included in this **Pull Request** failed to pass the **Installers Scan** test. This test is designed to ensure that the application installs on all environments without warnings. For further details on this error, see [binary validation errors](.\binary-validation-errors.md). |
+| **Binary-Validation-Error** | The application included in this **Pull Request** failed to pass the **Installers Scan** test. This test is designed to ensure that the application installs on all environments without warnings. For further details on this error, see [binary validation errors](binary-validation-errors.md). |
| **Error-Analysis-Timeout** | This label indicates that the **Binary-Validation-Test** test timed out. The **Pull Request** will get assigned to a Windows Package Manager developer to look at it. |
| **Error-Hash-Mismatch** | The submitted manifest could not be processed because the **InstallerSha256** hash provided for the **InstallerURL** did not match. Update the **InstallerSha256** in the **Pull Request** and try again. |
| **Error-Installer-Availability** | The validation service was unable to download the installer. This may be related to Azure IP ranges being blocked, or the installer URL may be incorrect. Check that the **InstallerURL** is correct and try again. If you feel this has failed in error, please add a comment and the **Pull Request** will get assigned to a Windows Package Manager developer to look investigate. |
| **Manifest-Path-Error** | The manifest files must be put into a specific folder structure. This label indicates a problem with the path of your submission. For example, the folder structure does not have the [required format](https://docs.microsoft.com/windows/package-manager/package/manifest?tabs=minschema%2Ccompschema). Update your manifest and path resubmit your **Pull Request**. |
| **Manifest-Validation-Error** | The submitted manifest contains a syntax error. Address the syntax issue with the manifest and re-submit. For details on the manifest format and schema see: [required format](https://docs.microsoft.com/windows/package-manager/package/manifest?tabs=minschema%2Ccompschema). |
| **PullRequest-Error** | The pull request is invalid because not all files submitted are under manifest folder or there is more than one package or version in the **Pull Request**. Update your **Pull Request** to address the issue and try again. |
-| **URL-Validation-Error** | The **URLs Validation Test** could not locate the URL and responded with a [HTTP error status code](https://docs.microsoft.com/troubleshoot/iis/http-status-code) (403 or 404), or the URL reputation test failed. You can identify which URL is in question by looking at the [Pull Request check details](.\winget-validation-troubleshooter.md). To address this issue, update the URLs in question to resolve the [HTTP error status code](https://docs.microsoft.com/troubleshoot/iis/http-status-code). If the issue is not due to [HTTP error status code](https://docs.microsoft.com/troubleshoot/iis/http-status-code) then you can [submit the URL for review](https://www.microsoft.com/wdsi/filesubmission/) to avoid the reputation failure. |
-| **Validation-Defender-Error** | During dynamic testing, Defender reported a problem. To reproduce this problem, install your application, then run a Defender full scan. If you can reproduce the problem, either fix the binary, or submit to this URL for false positive assistance. As stated in the following article,[Address false positives/negatives in Microsoft Defender for Endpoint Microsoft Docs](https://docs.microsoft.com/microsoft-365/security/defender-endpoint/defender-endpoint-false-positives-negatives?view=o365-worldwide), you can submit your binary for analysis to the [defender analysis web page](https://docs.microsoft.com/microsoft-365/security/defender-endpoint/defender-endpoint-false-positives-negatives?view=o365-worldwide#part-4-submit-a-file-for-analysis). If you are unable to reproduce, add a comment to get the Windows Package Manager developers to look at it. |
-| **Validation-Domain** | The test has determined the domain if the **InstallerURL** does not match the domain expected. The Windows Package Manager policies requires that the [InstallerUrl](https://docs.microsoft.com/windows/package-manager/package/manifest?tabs=minschema%2Ccompschema)comes directly from the ISVs release location. If you believe this is a false detection, add a comment to the **Pull Request** to get the Windows Package Manager developers to look at it. |
+| **URL-Validation-Error** | The **URLs Validation Test** could not locate the URL and responded with a [HTTP error status code](https://docs.microsoft.com/troubleshoot/iis/http-status-code) (403 or 404), or the URL reputation test failed. You can identify which URL is in question by looking at the [Pull Request check details](winget-validation-troubleshooter.md). To address this issue, update the URLs in question to resolve the [HTTP error status code](https://docs.microsoft.com/troubleshoot/iis/http-status-code). If the issue is not due to [HTTP error status code](https://docs.microsoft.com/troubleshoot/iis/http-status-code) then you can [submit the URL for review](https://www.microsoft.com/wdsi/filesubmission/) to avoid the reputation failure. |
+| **Validation-Defender-Error** | During dynamic testing, Defender reported a problem. To reproduce this problem, install your application, then run a Defender full scan. If you can reproduce the problem, either fix the binary, or submit to this URL for false positive assistance. As stated in the following article, [Address false positives/negatives in Microsoft Defender for Endpoint Microsoft Docs](https://docs.microsoft.com/microsoft-365/security/defender-endpoint/defender-endpoint-false-positives-negatives?view=o365-worldwide), you can submit your binary for analysis to the [defender analysis web page](https://docs.microsoft.com/microsoft-365/security/defender-endpoint/defender-endpoint-false-positives-negatives?view=o365-worldwide#part-4-submit-a-file-for-analysis). If you are unable to reproduce, add a comment to get the Windows Package Manager developers to look at it. |
+| **Validation-Domain** | The test has determined the domain if the **InstallerURL** does not match the domain expected. The Windows Package Manager policies requires that the [InstallerUrl](https://docs.microsoft.com/windows/package-manager/package/manifest?tabs=minschema%2Ccompschema) comes directly from the ISVs release location. If you believe this is a false detection, add a comment to the **Pull Request** to get the Windows Package Manager developers to look at it. |
| **Validation-Error** | Validation of the Windows Package Manager failed during manual approval. Look at the accompanying comment for next steps. |
| **Validation-Executable-Error** | During installation testing, the test was unable to locate the primary application. Make sure the application installs correctly on all platforms. If your application does not install an application, but should still be included in the repository, add a comment to the **Pull Request** to get the Windows Package Manager developers to look at it.|
| **Validation-Hash-Verification-Failed** | During installation testing, the application fails to install because the **InstallerSha256** no longer matches the **InstallerURL** hash. This can occur if the application is behind a vanity URL and the installer was updated without updating the **InstallerSha256**. To address this issue, update the **InstallerSha256** associated with the **InstallerURL** and submit again. |
| **Validation-HTTP-Error** | The URL used for the installer does not use the HTTPs protocol. Please update the **InstallerURL** to use HTTPS and resubmit the **Pull Request.** |
-| **Validation-Indirect-URL** | The URL is not coming directly from the ISVs server. Testing has determined a redirector has been used. This is not allowed because the Windows Package Manager policies require that the[InstallerUrl](https://docs.microsoft.com/windows/package-manager/package/manifest?tabs=minschema%2Ccompschema) comes directly from the ISVs release location. Remove the redirection and resubmit.
+| **Validation-Indirect-URL** | The URL is not coming directly from the ISVs server. Testing has determined a redirector has been used. This is not allowed because the Windows Package Manager policies require that the [InstallerUrl](https://docs.microsoft.com/windows/package-manager/package/manifest?tabs=minschema%2Ccompschema) comes directly from the ISVs release location. Remove the redirection and resubmit.
| **Validation-Installation-Error** | During manual validation of this package, there was a general error. Look at the accompanying comment for next steps.|
| **Validation-Merge-Conflict** | This package could not be validated due to a merge conflict. Please address the merge conflict and resubmit your **Pull Request.**
| **Validation-MSIX-Dependency** | The MSIX package has a dependency on package that could not be resolved. Update the package to include the missing components or add the dependency to the manifest file and resubmit the **Pull Request.**|
@@ -81,23 +81,23 @@ immediately. Some may trigger manual validation.
The following table lists **content policy labels**. If one of
the following labels is added, then something in the manifest metadata
triggered additional manual content review to ensure that the metadata
-is following the [Windows Package Manager policies](.\windows-package-manager-policies.md).
+is following the [Windows Package Manager policies](windows-package-manager-policies.md).
| **Label** | **Details** |
|--------------|-------------|
|<img width=180/>|<img width=500/>|
-| **Policy-Test-2.1** |Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#21-general-content-requirements) |
-| **Policy-Test-2.2** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#22-content-including-names-logos-original-and-third-party) |
-| **Policy-Test-2.3** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#23-risk-of-harm) |
-| **Policy-Test-2.4** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#24-defamatory-libelous-slanderous-and-threatening) |
-| **Policy-Test-2.5** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#25-offensive-content) |
-| **Policy-Test-2.6** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#26-alcohol-tobacco-weapons-and-drugs) |
-| **Policy-Test-2.7** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#27-adult-content) |
-| **Policy-Test-2.8** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#28-illegal-activity) |
-| **Policy-Test-2.9** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#29-excessive-profanity-and-inappropriate-content) |
-| **Policy-Test-2.10** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#210-countryregion-specific-requirements) |
-| **Policy-Test-2.11** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#211-age-ratings) |
-| **Policy-Test-2.12** | Manual review triggered see [Windows Package Manager Policies](.\windows-package-manager-policies.md#212-user-generated-content) |
+| **Policy-Test-2.1** |Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#21-general-content-requirements) |
+| **Policy-Test-2.2** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#22-content-including-names-logos-original-and-third-party) |
+| **Policy-Test-2.3** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#23-risk-of-harm) |
+| **Policy-Test-2.4** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#24-defamatory-libelous-slanderous-and-threatening) |
+| **Policy-Test-2.5** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#25-offensive-content) |
+| **Policy-Test-2.6** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#26-alcohol-tobacco-weapons-and-drugs) |
+| **Policy-Test-2.7** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#27-adult-content) |
+| **Policy-Test-2.8** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#28-illegal-activity) |
+| **Policy-Test-2.9** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#29-excessive-profanity-and-inappropriate-content) |
+| **Policy-Test-2.10** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#210-countryregion-specific-requirements) |
+| **Policy-Test-2.11** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#211-age-ratings) |
+| **Policy-Test-2.12** | Manual review triggered see [Windows Package Manager Policies](windows-package-manager-policies.md#212-user-generated-content) |
### Internal Labels
diff --git a/doc/windows/package-manager/winget/export.md b/doc/windows/package-manager/winget/export.md
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
The **export** command of the [winget](index.md) tool exports a JSON file of apps to a specified file. The **export** command users JSON as the format. The JSON schema used by **winget** can be found [here](https://aka.ms/winget-packages.schema.1.0.json).
-The **export** combined with the [**import**](.\import.md) command allows you to batch install applications on your PC.
+The **export** combined with the [**import**](import.md) command allows you to batch install applications on your PC.
The **export** command is often used to create a file that you can share with other developers, or for use when restoring your build environment.
@@ -36,7 +36,7 @@ The options allow you to customize the export experience to meet your needs.
|<div style="width:290px">Option</div> | Description |
|----------------|-------------|
| **-s, --source** | [optional] Specifies a source to export files from. Use this option when you only want files from a specific source. |
-| **--include-versions** | [optional] Includes the version of the app currently installed. Use this option if you want a specific version. By default, unless specified, [**import**](.\import.md) will use latest. |
+| **--include-versions** | [optional] Includes the version of the app currently installed. Use this option if you want a specific version. By default, unless specified, [**import**](import.md) will use latest. |
## JSON Schema
The driving force behind the **export** command is the JSON file. As mentioned, you can find the schema for the JSON file [here](https://aka.ms/winget-packages.schema.1.0.json).
diff --git a/doc/windows/package-manager/winget/features.md b/doc/windows/package-manager/winget/features.md
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
The **features** command of the [winget](index.md) tool displays a list of the experimental features available with your version of the Windows Package Manager.
-Each feature can be turned on individually by enabling the features through [**settings**](.\settings.md).
+Each feature can be turned on individually by enabling the features through [**settings**](settings.md).
You can find the latest up to date information features on the [experimental features](https://aka.ms/winget-experimentalfeatures) web page.
diff --git a/doc/windows/package-manager/winget/import.md b/doc/windows/package-manager/winget/import.md
@@ -10,7 +10,7 @@ ms.localizationpriority: medium
[!INCLUDE [preview-note](../../includes/package-manager-preview.md)]
-The **import** command of the [winget](index.md) tool imports a JSON file of apps to install. The **import** command combined with the [**export**](.\export.md) command allows you to batch install applications on your PC.
+The **import** command of the [winget](index.md) tool imports a JSON file of apps to install. The **import** command combined with the [**export**](export.md) command allows you to batch install applications on your PC.
The **import** command is often used to share your developer environment or build up your PC image with your favorite apps.
diff --git a/doc/windows/package-manager/winget/index.md b/doc/windows/package-manager/winget/index.md
@@ -31,9 +31,9 @@ There are several ways to install the **winget** tool:
Installer behavior can be different depending on whether you are running **winget** with administrator privileges.
-* When running **winget** without administrator privileges, some applications may [require elevation](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/) to install. When the installer runs, Windows will prompt you to [elevate](https://docs.microsoft.com/windows/security/identity-protection/user-account-control). If you choose not to elevate, the application will fail to install.
+* When running **winget** without administrator privileges, some applications may [require elevation](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works) to install. When the installer runs, Windows will prompt you to [elevate](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works). If you choose not to elevate, the application will fail to install.
-* When running **winget** in an Administrator Command Prompt, you will not see [elevation prompts](/windows/security/identity-protection/user-account-control/how-user-account-control-works) if the application requires it. Always use caution when running your command prompt as an administrator, and only install applications you trust.
+* When running **winget** in an Administrator Command Prompt, you will not see [elevation prompts](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works) if the application requires it. Always use caution when running your command prompt as an administrator, and only install applications you trust.
## Use winget
diff --git a/doc/windows/package-manager/winget/list.md b/doc/windows/package-manager/winget/list.md
@@ -12,7 +12,7 @@ ms.localizationpriority: medium
The **list** command of the [winget](index.md) tool displays a list of the applications currently installed on your computer. The list command will show apps that were installed through the Windows Package Manager as well as apps that were installed by other means.
-In addition, the **list** command will also display if an update is available for an app, and you can use the [**upgrade**](.\upgrade.md) command to update the app.
+In addition, the **list** command will also display if an update is available for an app, and you can use the [**upgrade**](upgrade.md) command to update the app.
The **list** command also supports filters which can be used to limit your list query.
diff --git a/doc/windows/package-manager/winget/uninstall.md b/doc/windows/package-manager/winget/uninstall.md
@@ -72,7 +72,7 @@ If the query provided to **winget** does not result in a single application to u
## Uninstalling apps not installed with Windows Package Manager
-As mentioned in [**list**](.\list.md), the **winget list** command will display more than just apps installed with the **winget**. Therefore you can use these commands to quickly and easily remove apps from your PC.
+As mentioned in [**list**](list.md), the **winget list** command will display more than just apps installed with the **winget**. Therefore you can use these commands to quickly and easily remove apps from your PC.
In this example, **list** was used to find the application, and then the **id** was passed in as part of uninstall.
diff --git a/doc/windows/package-manager/winget/upgrade.md b/doc/windows/package-manager/winget/upgrade.md
@@ -10,7 +10,7 @@ ms.localizationpriority: medium
[!INCLUDE [preview-note](../../includes/package-manager-preview.md)]
-The **upgrade** command of the [winget](index.md) tool upgrades the specified application. Optionally, you may use the [**list**](.\list.md) command to identify the application you want to upgrade.
+The **upgrade** command of the [winget](index.md) tool upgrades the specified application. Optionally, you may use the [**list**](list.md) command to identify the application you want to upgrade.
The **upgrade** command requires that you specify the exact string to upgrade. If there is any ambiguity, you will be prompted to further filter the **upgrade** command to an exact application.
@@ -71,9 +71,9 @@ winget upgrade --all
## Using **list** and **upgrade**
-It is common to use the [**list**](.\list.md) command to identify apps in need of an update, and then to use **upgrade** to install the latest.
+It is common to use the [**list**](list.md) command to identify apps in need of an update, and then to use **upgrade** to install the latest.
-In the example below you will see [**list**](.\list.md) identifies that an update is available for Microsoft.WindowsTerminalPreview, and then the user uses **upgrade** to update the application.
+In the example below you will see [**list**](list.md) identifies that an update is available for Microsoft.WindowsTerminalPreview, and then the user uses **upgrade** to update the application.
diff --git a/doc/windows/package-manager/winget/validate.md b/doc/windows/package-manager/winget/validate.md
@@ -10,7 +10,7 @@ ms.localizationpriority: medium
[!INCLUDE [preview-note](../../includes/package-manager-preview.md)]
-The **validate** command of the [winget](index.md) tool validates a [manifest](../package/manifest.md) for submitting software to the **Microsoft Community Package Manifest Repository** on GitHub. The manifest must be a YAML file that follows the [specification](https://github.com/microsoft/winget-pkgs/YamlSpec.md).
+The **validate** command of the [winget](index.md) tool validates a [manifest](../package/manifest.md) for submitting software to the **Microsoft Community Package Manifest Repository** on GitHub. The manifest must be a YAML file that follows the [specification](/doc/ManifestSpecv1.0.md).
## Usage
