Skip to content

Commit 95d09ed

Browse files
committed
(#426) Address review comments
1 parent d193c46 commit 95d09ed

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/content/docs/en-us/community-repository/maintainers/common-errors.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
---
22
order: 50
33
xref: ccr-common-errors
4-
title: Common Errors Encountered
5-
description: descriptiono
4+
title: Common Errors and Resolutions
5+
description: Common Errors and Resolutions encountered with pushing packages to the Chocolatey Community Repository
66
---
77
import Callout from '@choco-astro/components/Callout.astro';
88
import Iframe from '@choco-astro/components/Iframe.astro';
99
import Xref from '@components/Xref.astro';
1010

11-
## You've pushed a package, but got an error?
11+
## Have you pushed a package and gotten an error?
1212

1313
Once you've pushed a package to the Chocolatey Community Repository, Chocolatey CLI will report if it was successful or not. If for any reason it's not successful, it will report the error code and any response that it received. Sometimes the error text is not fully received due to various network issues. Below is a list of HTTP responses and what it could mean.
1414

1515
## Error 400 Bad Request
1616

17-
Can occur if the API Key is not a validly formatted GUID, or the package you've attempted to push contains a non-normalized version number.
17+
Can occur if the API Key is not a correctly formatted GUID, or the package you've attempted to push contains a non-normalized version number.
1818

1919
## Error 403 Unauthorized
2020

@@ -41,7 +41,7 @@ Package is too large.
4141
## Error 500 Internal Server Error
4242

4343
If you receive a `500 Internal Server Error` when pushing a package, you may have a malformed package that the server was unable to process.
44-
One such case is documented in a [GitHub issue](https://github.com/chocolatey/home/issues/303).
44+
One such case is documented in this [GitHub issue](https://github.com/chocolatey/home/issues/303).
4545

4646
Make sure that none of the `<file ...>` entries in the `nuspec` file of your package have name collisions with other files or folders being packed.
4747
This is usually rare but can be encountered more commonly if you are trying to pack files which don't have a file extension.

0 commit comments

Comments
 (0)