[neon-notifications] Changes in repo-metadata

[Neon CI]

commit 614be177a5dfbad0ea316c43bde20bd2ef85cd04
Author: Sandro Knauß <sknauss at kde.org>
Date:   Wed Sep 23 12:47:14 2020 +0200

    bug-database and bug-submit keys will be generated by project-api!2

diff --git a/README.md b/README.md
index 01867c05..f4c60921 100644
--- a/README.md
+++ b/README.md
@@ -27,10 +27,7 @@ First, the mandatory fields. The fields `name` and `description` are to provide
 
 If your project has a repo, you'll need to set `hasrepo` to `true`. If `hasrepo` is `true`, then you'll have to define two more fields - `repopath`, a path to the repository on disk, and `repoactive`, stating if the repo is active.
 
-`bug-database`: A URL to the list of known bugs for the project.
-`bug-summit`: A URL that is the place where new bug reports should be sent.
-
-The bugzilla dictonary tells what is the corrent product/component for bugzilla. `__do_not_use-legacy-product` points to obsolute product, that was used in past.
+The `bugzilla` dictonary tells what is the corrent `product`/`component` for bugzilla. `__do_not_use-legacy-product` points to obsolute product, that was used in past.
 
 The next file you'll deal with is `i18n.json`. This file is much simpler to interpret. Here's an example: