Subsurface-*x86_64.AppImage.zsync

To cover the case where we don't have a version in the filename. Thanks @TheAssassin for pointing it out with great patience

Author: probonopd

draft.md

@@ -202,7 +202,7 @@ For an overview about [zsync] and how to create `.zsync` files, see [http://zsyn
 The __GitHub Releases__ transport extends the [zsync] transport in that it uses version information from [GitHub Releases](https://help.github.com/articles/about-releases/). Its [update information] is in the form
 
 ```
-gh-releases-zsync|probono|AppImages|latest|Subsurface-*-x86_64.AppImage.zsync
+gh-releases-zsync|probono|AppImages|latest|Subsurface-*x86_64.AppImage.zsync
 ```
 
 If an [AppImage] has [update information] embedded for this transport mechanism, then the following fields **MUST** be used; separated by a "|" character:
@@ -213,7 +213,7 @@ Transport mechanism | String | `gh-releases-zsync` | [zsync] file and [AppImage]
 Bintray username | String | `probono` | Name of the GitHub user or organization of the account where the [zsync] file and [AppImage] are stored
 Bintray repository | String | `AppImages` | Name of the GitHub repository in which the [zsync] file and [AppImage] are stored
 Release name | String | `latest` | Name of the release. `latest` will automatically use the latest release as determined by the GitHub API
-Filename | String | `Subsurface-*-x86_64.AppImage.zsync` | Filename of the [zsync] file on GitHub, `*` is a wildcard
+Filename | String | `Subsurface-*x86_64.AppImage.zsync` | Filename of the [zsync] file on GitHub, `*` is a wildcard
 
 **Please note that pre-releases are not being considered when using `latest`.** You will have to explicitly provide the name of a release. When using e.g., [uploadtool](https://github.com/probonopd/uploadtool), the name of the release created will always be `continuous`, hence, you can just specify that value instead of `latest`.