diff --git a/core/includes/common.inc b/core/includes/common.inc
index e73924d..a1834f6 100644
--- a/core/includes/common.inc
+++ b/core/includes/common.inc
@@ -33,37 +33,6 @@
 use Drupal\Core\Session\AnonymousUserSession;
 
 /**
- * @defgroup php_wrappers PHP wrapper functions
- * @{
- * Functions that are wrappers or custom implementations of PHP functions.
- *
- * Certain PHP functions should not be used in Drupal. Instead, Drupal's
- * replacement functions should be used.
- *
- * For example, for improved or more secure UTF8-handling, or RFC-compliant
- * handling of URLs in Drupal.
- *
- * For ease of use and memorizing, all these wrapper functions use the same name
- * as the original PHP function, but prefixed with "drupal_". Beware, however,
- * that not all wrapper functions support the same arguments as the original
- * functions.
- *
- * You should always use these wrapper functions in your code.
- *
- * Wrong:
- * @code
- *   $my_substring = substr($original_string, 0, 5);
- * @endcode
- *
- * Correct:
- * @code
- *   $my_substring = drupal_substr($original_string, 0, 5);
- * @endcode
- *
- * @}
- */
-
-/**
  * Return status for saving which involved creating a new item.
  */
 const SAVED_NEW = 1;
@@ -296,12 +265,6 @@ function drupal_get_feeds() {
 }
 
 /**
- * @defgroup http_handling HTTP handling
- * @{
- * Functions to properly handle HTTP responses.
- */
-
-/**
  * Prepares a 'destination' URL query parameter for use with url().
  *
  * Used to direct the user back to the referring page after completing a form.
@@ -339,16 +302,6 @@ function drupal_get_destination() {
 }
 
 /**
- * @} End of "defgroup http_handling".
- */
-
-/**
- * @defgroup validation Input validation
- * @{
- * Functions to validate user input.
- */
-
-/**
  * Verifies the syntax of the given email address.
  *
  * This uses the
@@ -365,19 +318,6 @@ function valid_email_address($mail) {
 }
 
 /**
- * @} End of "defgroup validation".
- */
-
-/**
- * @defgroup sanitization Sanitization functions
- * @{
- * Functions to sanitize values.
- *
- * See http://drupal.org/writing-secure-code for information
- * on writing secure code.
- */
-
-/**
  * Strips dangerous protocols from a URI and encodes it for output to HTML.
  *
  * @param $uri
@@ -400,16 +340,6 @@ function check_url($uri) {
 }
 
 /**
- * @} End of "defgroup sanitization".
- */
-
-/**
- * @defgroup format Formatting
- * @{
- * Functions to format numbers, strings, dates, etc.
- */
-
-/**
  * Formats an RSS channel.
  *
  * Arbitrary elements may be added using the $args associative array.
@@ -692,10 +622,6 @@ function _format_date_callback(array $matches = NULL, $new_langcode = NULL) {
 }
 
 /**
- * @} End of "defgroup format".
- */
-
-/**
  * Generates an internal or external URL.
  *
  * When creating links in modules, consider whether l() could be a better
@@ -4194,59 +4120,4 @@ function drupal_get_filetransfer_info() {
     uasort($info, array('Drupal\Component\Utility\SortArray', 'sortByWeightElement'));
   }
   return $info;
-}
-
-/**
- * @defgroup queue Queue operations
- * @{
- * Queue items to allow later processing.
- *
- * The queue system allows placing items in a queue and processing them later.
- * The system tries to ensure that only one consumer can process an item.
- *
- * Before a queue can be used it needs to be created by
- * Drupal\Core\Queue\QueueInterface::createQueue().
- *
- * Items can be added to the queue by passing an arbitrary data object to
- * Drupal\Core\Queue\QueueInterface::createItem().
- *
- * To process an item, call Drupal\Core\Queue\QueueInterface::claimItem() and
- * specify how long you want to have a lease for working on that item.
- * When finished processing, the item needs to be deleted by calling
- * Drupal\Core\Queue\QueueInterface::deleteItem(). If the consumer dies, the
- * item will be made available again by the Drupal\Core\Queue\QueueInterface
- * implementation once the lease expires. Another consumer will then be able to
- * receive it when calling Drupal\Core\Queue\QueueInterface::claimItem().
- * Due to this, the processing code should be aware that an item might be handed
- * over for processing more than once.
- *
- * The $item object used by the Drupal\Core\Queue\QueueInterface can contain
- * arbitrary metadata depending on the implementation. Systems using the
- * interface should only rely on the data property which will contain the
- * information passed to Drupal\Core\Queue\QueueInterface::createItem().
- * The full queue item returned by Drupal\Core\Queue\QueueInterface::claimItem()
- * needs to be passed to Drupal\Core\Queue\QueueInterface::deleteItem() once
- * processing is completed.
- *
- * There are two kinds of queue backends available: reliable, which preserves
- * the order of messages and guarantees that every item will be executed at
- * least once. The non-reliable kind only does a best effort to preserve order
- * in messages and to execute them at least once but there is a small chance
- * that some items get lost. For example, some distributed back-ends like
- * Amazon SQS will be managing jobs for a large set of producers and consumers
- * where a strict FIFO ordering will likely not be preserved. Another example
- * would be an in-memory queue backend which might lose items if it crashes.
- * However, such a backend would be able to deal with significantly more writes
- * than a reliable queue and for many tasks this is more important. See
- * aggregator_cron() for an example of how to effectively utilize a
- * non-reliable queue. Another example is doing Twitter statistics -- the small
- * possibility of losing a few items is insignificant next to power of the
- * queue being able to keep up with writes. As described in the processing
- * section, regardless of the queue being reliable or not, the processing code
- * should be aware that an item might be handed over for processing more than
- * once (because the processing code might time out before it finishes).
- */
-
-/**
- * @} End of "defgroup queue".
- */
+}
\ No newline at end of file
diff --git a/core/includes/menu.inc b/core/includes/menu.inc
index ae35c07..77fd447 100644
--- a/core/includes/menu.inc
+++ b/core/includes/menu.inc
@@ -10,258 +10,6 @@
 use Drupal\Core\Template\Attribute;
 
 /**
- * @defgroup menu Menu and routing system
- * @{
- * Define the navigation menus, and route page requests to code based on URLs.
- *
- * @section sec_overview Overview and terminology
- * The Drupal routing system defines how Drupal responds to URL requests that
- * the web server passes on to Drupal. The routing system is based on the
- * @link http://symfony.com Symfony framework. @endlink The central idea is
- * that Drupal subsystems and modules can register routes (basically, URL
- * paths and context); they can also register to respond dynamically to
- * routes, for more flexibility. When Drupal receives a URL request, it will
- * attempt to match the request to a registered route, and query dynamic
- * responders. If a match is made, Drupal will then instantiate the required
- * classes, gather the data, format it, and send it back to the web browser.
- * Otherwise, Drupal will return a 404 or 403 response.
- *
- * The menu system uses routes; it is used for navigation menus, local tasks,
- * local actions, and contextual links:
- * - Navigation menus are hierarchies of menu links; links point to routes or
- *   URLs.
- * - Menu links and their hierarchies can be defined by Drupal subsystems
- *   and modules, or created in the user interface using the Menu UI module.
- * - Local tasks are groups of related routes. Local tasks are usually rendered
- *   as a group of tabs.
- * - Local actions are used for operations such as adding a new item on a page
- *   that lists items of some type. Local actions are usually rendered as
- *   buttons.
- * - Contextual links are actions that are related to sections of rendered
- *   output, and are usually rendered as a pop-up list of links. The
- *   Contextual Links module handles the gathering and rendering of contextual
- *   links.
- *
- * The following sections of this topic provide an overview of the routing and
- * menu APIs. For more detailed information, see
- * https://www.drupal.org/developing/api/8/routing and
- * https://www.drupal.org/developing/api/8/menu
- *
- * @section sec_register Registering simple routes
- * To register a route, add lines similar to this to a module_name.routing.yml
- * file in your top-level module directory:
- * @code
- * dblog.overview:
- *   path: '/admin/reports/dblog'
- *   defaults:
- *     _content: '\Drupal\dblog\Controller\DbLogController::overview'
- *     _title: 'Recent log messages'
- *   requirements:
- *     _permission: 'access site reports'
- * @endcode
- * Some notes:
- * - The first line is the machine name of the route. Typically, it is prefixed
- *   by the machine name of the module that defines the route, or the name of
- *   a subsystem.
- * - The 'path' line gives the URL path of the route (relative to the site's
- *   base URL).
- * - The 'defaults' section tells how to build the main content of the route,
- *   and can also give other information, such as the page title and additional
- *   arguments for the route controller method. There are several possibilities
- *   for how to build the main content, including:
- *   - _content: A callable, usually a method on a page controller class
- *     (see @ref sec_controller below for details).
- *   - _controller: A callable, usually a method on a page controller class
- *     (see @ref sec_controller below for details).
- *   - _form: A form controller class. See the
- *     @link form_api Form API topic @endlink for more information about
- *     form controllers.
- *   - _entity_form: A form for editing an entity. See the
- *     @link entity_api Entity API topic @endlink for more information.
- * - The 'requirements' section is used in Drupal to give access permission
- *   instructions (it has other uses in the Symfony framework). Most
- *   routes have a simple permission-based access scheme, as shown in this
- *   example. See the @link user_api Permission system topic @endlink for
- *   more information about permissions.
- *
- * See https://www.drupal.org/node/2092643 for more details about *.routing.yml
- * files, and https://www.drupal.org/node/2122201 for information on how to
- * set up dynamic routes.
- *
- * @section sec_placeholders Defining routes with placeholders
- * Some routes have placeholders in them, and these can also be defined in a
- * module_name.routing.yml file, as in this example from the Block module:
- * @code
- * block.admin_edit:
- *   path: '/admin/structure/block/manage/{block}'
- *   defaults:
- *     _entity_form: 'block.default'
- *     _title: 'Configure block'
- *   requirements:
- *     _entity_access: 'block.update'
- * @endcode
- * In the path, '{block}' is a placeholder - it will be replaced by the
- * ID of the block that is being configured by the entity system. See the
- * @link entity_api Entity API topic @endlink for more information.
- *
- * @section sec_controller Route controllers for simple routes
- * For simple routes, after you have defined the route in a *.routing.yml file
- * (see @ref sec_register above), the next step is to define a page controller
- * class and method. Page controller classes do not necessarily need to
- * implement any particular interface or extend any particular base class. The
- * only requirement is that the method specified in your *.routing.yml file
- * return one of the following, depending on whether you specified _content or
- * _controller in the routing file defaults section:
- * - A render array (see the
- *   @link theme_render Theme and render topic @endlink for more information),
- *   if _content is used in the routing file.
- * - A \Drupal\Core\Page\HtmlFragmentInterface object (fragment or page), if
- *   _content is used in the routing file.
- * - A \Symfony\Component\HttpFoundation\Response object, if _controller is
- *   used in the routing file.
- * As a note, if your module registers multiple simple routes, it is usual
- * (and usually easiest) to put all of their methods on one controller class.
- *
- * Most controllers will need to display some information stored in the Drupal
- * database, which will involve using one or more Drupal services (see the
- * @link container Services and container topic @endlink). In order to properly
- * inject services, a controller should implement
- * \Drupal\Core\DependencyInjection\ContainerInjectionInterface; simple
- * controllers can do this by extending the
- * \Drupal\Core\Controller\ControllerBase class. See
- * \Drupal\dblog\Controller\DbLogController for a straightforward example of
- * a controller class.
- *
- * @section sec_links Defining menu links for the administrative menu
- * Routes for administrative tasks can be added to the main Drupal
- * administrative menu hierarchy. To do this, add lines like the following to a
- * module_name.menu_links.yml file (in the top-level directory for your module):
- * @code
- * dblog.overview:
- *   title: 'Recent log messages'
- *   parent: system.admin_reports
- *   description: 'View events that have recently been logged.'
- *   route_name: dblog.overview
- *   weight: -1
- * @endcode
- * Some notes:
- * - The first line is the machine name for your menu link, which usually
- *   matches the machine name of the route (given in the 'route_name' line).
- * - parent: The machine name of the menu link that is the parent in the
- *   administrative hierarchy. See system.menu_links.yml to find the main
- *   skeleton of the hierarchy.
- * - weight: Lower (negative) numbers come before higher (positive) numbers,
- *   for menu items with the same parent.
- *
- * Menu items from other modules can be altered using
- * hook_menu_link_defaults_alter().
- *
- * @todo Derivatives will probably be defined for these; when they are, add
- *   documentation here.
- *
- * @section sec_tasks Defining groups of local tasks (tabs)
- * Local tasks appear as tabs on a page when there are at least two defined for
- * a route, including the base route as the main tab, and additional routes as
- * other tabs. Static local tasks can be defined by adding lines like the
- * following to a module_name.local_tasks.yml file (in the top-level directory
- * for your module):
- * @code
- * book.admin:
- *   route_name: book.admin
- *   title: 'List'
- *   base_route: book.admin
- * book.settings:
- *   route_name: book.settings
- *   title: 'Settings'
- *   base_route: book.admin
- *   weight: 100
- * @endcode
- * Some notes:
- * - The first line is the machine name for your local task, which usually
- *   matches the machine name of the route (given in the 'route_name' line).
- * - base_route: The machine name of the main task (tab) for the set of local
- *   tasks.
- * - weight: Lower (negative) numbers come before higher (positive) numbers,
- *   for tasks on the same base route. If there is a tab whose route
- *   matches the base route, that will be the default/first tab shown.
- *
- * Local tasks from other modules can be altered using
- * hook_menu_local_tasks_alter().
- *
- * @todo Derivatives are in flux for these; when they are more stable, add
- *   documentation here.
- *
- * @section sec_actions Defining local actions for routes
- * Local actions can be defined for operations related to a given route. For
- * instance, adding content is a common operation for the content management
- * page, so it should be a local action. Static local actions can be
- * defined by adding lines like the following to a
- * module_name.local_actions.yml file (in the top-level directory for your
- * module):
- * @code
- * node.add_page:
- *   route_name: node.add_page
- *   title: 'Add content'
- *   appears_on:
- *     - system.admin_content
- * @endcode
- * Some notes:
- * - The first line is the machine name for your local action, which usually
- *   matches the machine name of the route (given in the 'route_name' line).
- * - appears_on: Machine names of one or more routes that this local task
- *   should appear on.
- *
- * Local actions from other modules can be altered using
- * hook_menu_local_actions_alter().
- *
- * @todo Derivatives are in flux for these; when they are more stable, add
- *   documentation here.
- *
- * @section sec_contextual Defining contextual links
- * Contextual links are displayed by the Contextual Links module for user
- * interface elements whose render arrays have a '#contextual_links' element
- * defined. For example, a block render array might look like this, in part:
- * @code
- * array(
- *   '#contextual_links' => array(
- *     'block' => array(
- *       'route_parameters' => array('block' => $entity->id()),
- *     ),
- *   ),
- * @endcode
- * In this array, the outer key 'block' defines a "group" for contextual
- * links, and the inner array provides values for the route's placeholder
- * parameters (see @ref sec_placeholders above).
- *
- * To declare that a defined route should be a contextual link for a
- * contextual links group, put lines like the following in a
- * module_name.contextual_links.yml file (in the top-level directory for your
- * module):
- * @code
- * block_configure:
- *   title: 'Configure block'
- *   route_name: 'block.admin_edit'
- *   group: 'block'
- * @endcode
- * Some notes:
- * - The first line is the machine name for your contextual link, which usually
- *   matches the machine name of the route (given in the 'route_name' line).
- * - group: This needs to match the link group defined in the render array.
- *
- * Contextual links from other modules can be altered using
- * hook_contextual_links_alter().
- *
- * @todo Derivatives are in flux for these; when they are more stable, add
- *   documentation here.
- */
-
-/**
- * @defgroup menu_tree_parameters Menu tree parameters
- * @{
- * Parameters for a menu tree.
- */
-
-/**
  * The maximum depth of a menu links tree - matches the number of p columns.
  *
  * @todo Move this constant to MenuLinkStorage along with all the tree
@@ -269,11 +17,6 @@
  */
 const MENU_MAX_DEPTH = 9;
 
-
-/**
- * @} End of "defgroup menu_tree_parameters".
- */
-
 /**
  * Reserved key to identify the most specific menu link for a given path.
  *
@@ -389,7 +132,6 @@ function template_preprocess_menu_tree(&$variables) {
  *   - tree: An HTML string containing the tree's items.
  *
  * @see template_preprocess_menu_tree()
- * @ingroup themeable
  */
 function theme_menu_tree($variables) {
   return '<ul class="menu">' . $variables['tree'] . '</ul>';
@@ -402,7 +144,6 @@ function theme_menu_tree($variables) {
  *   An associative array containing:
  *   - element: Structured array data for a menu link.
  *
- * @ingroup themeable
  */
 function theme_menu_link(array $variables) {
   $element = $variables['element'];
@@ -426,7 +167,6 @@ function theme_menu_link(array $variables) {
  *       keys.
  *     - #active: A boolean indicating whether the local task is active.
  *
- * @ingroup themeable
  */
 function theme_menu_local_task($variables) {
   $link = $variables['element']['#link'];
@@ -469,7 +209,6 @@ function theme_menu_local_task($variables) {
  *     - #link: A menu link array with 'title', 'href', and 'localized_options'
  *       keys.
  *
- * @ingroup themeable
  */
 function theme_menu_local_action($variables) {
   $link = $variables['element']['#link'];
@@ -722,7 +461,6 @@ function menu_local_tabs() {
  *     - primary: (optional) An array of local tasks (tabs).
  *     - secondary: (optional) An array of local tasks (tabs).
  *
- * @ingroup themeable
  * @see menu_local_tasks()
  */
 function theme_menu_local_tasks(&$variables) {
@@ -1094,8 +832,4 @@ function _menu_set_expanded_menus() {
   }
 
   \Drupal::state()->set('menu_expanded', $names);
-}
-
-/**
- * @} End of "defgroup menu".
- */
+}
\ No newline at end of file
diff --git a/core/modules/file/file.module b/core/modules/file/file.module
index 760a583..aa808b5 100644
--- a/core/modules/file/file.module
+++ b/core/modules/file/file.module
@@ -1826,12 +1826,6 @@ function file_icon_map(File $file) {
 }
 
 /**
- * @defgroup file-module-api File module public API functions
- * @{
- * These functions may be used to determine if and where a file is in use.
- */
-
-/**
  * Retrieves a list of references to a file.
  *
  * @param \Drupal\file\File $file
@@ -1929,10 +1923,6 @@ function file_get_file_references(File $file, FieldDefinitionInterface $field =
 }
 
 /**
- * @} End of "defgroup file-module-api".
- */
-
-/**
  * Implements hook_permission().
  */
 function file_permission() {
diff --git a/core/modules/system/system.api.php b/core/modules/system/system.api.php
index 461c431..2eea30d 100644
--- a/core/modules/system/system.api.php
+++ b/core/modules/system/system.api.php
@@ -9,11 +9,6 @@
 use Drupal\Core\Utility\UpdateException;
 
 /**
- * @addtogroup hooks
- * @{
- */
-
-/**
  * Defines one or more hooks that are exposed by a module.
  *
  * Normally hooks do not need to be explicitly defined. However, by declaring a
@@ -438,7 +433,6 @@ function hook_page_build(&$page) {
  *   - options: (optional) An array of options to be passed to l() when
  *     generating a link from this menu item.
  *
- * @ingroup menu
  */
 function hook_menu_link_defaults_alter(&$links) {
   // Change the weight and title of the user.logout link.
@@ -514,7 +508,6 @@ function hook_menu_local_tasks(&$data, $route_name) {
  *
  * @see hook_menu_local_tasks()
  *
- * @ingroup menu
  */
 function hook_menu_local_tasks_alter(&$data, $route_name) {
 }
@@ -528,7 +521,6 @@ function hook_menu_local_tasks_alter(&$data, $route_name) {
  * @see \Drupal\Core\Menu\LocalActionInterface
  * @see \Drupal\Core\Menu\LocalActionManager
  *
- * @ingroup menu
  */
 function hook_menu_local_actions_alter(&$local_actions) {
 }
@@ -579,7 +571,6 @@ function hook_local_tasks_alter(&$local_tasks) {
  *
  * @see \Drupal\Core\Menu\ContextualLinkManager
  *
- * @ingroup menu
  */
 function hook_contextual_links_alter(array &$links, $group, array $route_parameters) {
   if ($group == 'menu') {
@@ -975,7 +966,6 @@ function hook_system_info_alter(array &$info, \Drupal\Core\Extension\Extension $
  *     site. Use the 'description' key instead to provide any information that
  *     is specific to the permission you are defining.
  *
- * @ingroup user_api
  */
 function hook_permission() {
   return array(
@@ -1710,7 +1700,6 @@ function hook_requirements($phase) {
  *
  * @see hook_schema_alter()
  *
- * @ingroup schemaapi
  */
 function hook_schema() {
   $schema['node'] = array(
@@ -1781,7 +1770,6 @@ function hook_schema() {
  * @param $schema
  *   Nested array describing the schemas for all modules.
  *
- * @ingroup schemaapi
  */
 function hook_schema_alter(&$schema) {
   // Add field to existing schema.
@@ -2628,7 +2616,6 @@ function hook_token_info_alter(&$data) {
  * @see batch_set()
  * @see batch_process()
  *
- * @ingroup batch
  */
 function hook_batch_alter(&$batch) {
 }
@@ -2836,152 +2823,3 @@ function hook_config_import_steps_alter(&$sync_steps, \Drupal\Core\Config\Config
     $sync_steps[] = '_additional_configuration_step';
   }
 }
-
-/**
- * @} End of "addtogroup hooks".
- */
-
-/**
- * @defgroup update_api Update versions of API functions
- * @{
- * Functions that are similar to normal API functions, but do not invoke hooks.
- *
- * These simplified versions of core API functions are provided for use by
- * update functions (hook_update_N() implementations).
- *
- * During database updates the schema of any module could be out of date. For
- * this reason, caution is needed when using any API function within an update
- * function - particularly CRUD functions, functions that depend on the schema
- * (for example by using drupal_write_record()), and any functions that invoke
- * hooks.
- *
- * Instead, a simplified utility function should be used. If a utility version
- * of the API function you require does not already exist, then you should
- * create a new function. The new utility function should be named
- * _update_N_mymodule_my_function(). N is the schema version the function acts
- * on (the schema version is the number N from the hook_update_N()
- * implementation where this schema was introduced, or a number following the
- * same numbering scheme), and mymodule_my_function is the name of the original
- * API function including the module's name.
- *
- * Examples:
- * - _update_8001_mymodule_save(): This function performs a save operation
- *   without invoking any hooks using the original 8.x schema.
- * - _update_8002_mymodule_save(): This function performs the same save
- *   operation using an updated 8.x schema.
- *
- * The utility function should not invoke any hooks, and should perform database
- * operations using functions from the
- * @link database Database abstraction layer, @endlink
- * like db_insert(), db_update(), db_delete(), db_query(), and so on.
- *
- * If a change to the schema necessitates a change to the utility function, a
- * new function should be created with a name based on the version of the schema
- * it acts on. See _update_8002_bar_get_types() and _update_8003_bar_get_types()
- * in the code examples that follow.
- *
- * For example, foo.install could contain:
- * @code
- * function foo_update_dependencies() {
- *   // foo_update_8010() needs to run after bar_update_8002().
- *   $dependencies['foo'][8010] = array(
- *     'bar' => 8002,
- *   );
- *
- *   // foo_update_8036() needs to run after bar_update_8003().
- *   $dependencies['foo'][8036] = array(
- *     'bar' => 8003,
- *   );
- *
- *   return $dependencies;
- * }
- *
- * function foo_update_8002() {
- *   // No updates have been run on the {bar_types} table yet, so this needs
- *   // to work with the original 8.x schema.
- *   foreach (_update_8001_bar_get_types() as $type) {
- *     // Rename a variable.
- *   }
- * }
- *
- * function foo_update_8010() {
- *    // Since foo_update_8010() is going to run after bar_update_8002(), it
- *    // needs to operate on the new schema, not the old one.
- *    foreach (_update_8002_bar_get_types() as $type) {
- *      // Rename a different variable.
- *    }
- * }
- *
- * function foo_update_8036() {
- *   // This update will run after bar_update_8003().
- *   foreach (_update_8003_bar_get_types() as $type) {
- *   }
- * }
- * @endcode
- *
- * And bar.install could contain:
- * @code
- * function bar_update_8002() {
- *   // Type and bundle are confusing, so we renamed the table.
- *   db_rename_table('bar_types', 'bar_bundles');
- * }
- *
- * function bar_update_8003() {
- *   // Database table names should be singular when possible.
- *   db_rename_table('bar_bundles', 'bar_bundle');
- * }
- *
- * function _update_8001_bar_get_types() {
- *   db_query('SELECT * FROM {bar_types}')->fetchAll();
- * }
- *
- * function _update_8002_bar_get_types() {
- *   db_query('SELECT * FROM {bar_bundles'})->fetchAll();
- * }
- *
- * function _update_8003_bar_get_types() {
- *   db_query('SELECT * FROM {bar_bundle}')->fetchAll();
- * }
- * @endcode
- *
- * @see hook_update_N()
- * @see hook_update_dependencies()
- */
-
-/**
- * @} End of "defgroup update_api".
- */
-
-/**
- * @defgroup annotation Annotations
- * @{
- * Annotations for class discovery and metadata description.
- *
- * The Drupal plugin system has a set of reusable components that developers
- * can use, override, and extend in their modules. Most of the plugins use
- * annotations, which let classes register themselves as plugins and describe
- * their metadata. (Annotations can also be used for other purposes, though
- * at the moment, Drupal only uses them for the plugin system.)
- *
- * To annotate a class as a plugin, add code similar to the following to the
- * end of the documentation block immediately preceding the class declaration:
- * @code
- * * @ContentEntityType(
- * *   id = "comment",
- * *   label = @Translation("Comment"),
- * *   ...
- * *   base_table = "comment"
- * * )
- * @endcode
- *
- * Note that you must use double quotes; single quotes will not work in
- * annotations.
- *
- * The available annotation classes are listed in this topic, and can be
- * identified when you are looking at the Drupal source code by having
- * "@ Annotation" in their documentation blocks (without the space after @). To
- * find examples of annotation for a particular annotation class, such as
- * EntityType, look for class files that have an @ annotation section using the
- * annotation class.
- * @}
- */
diff --git a/core/modules/update/update.manager.inc b/core/modules/update/update.manager.inc
index 86872da..7a661b3 100644
--- a/core/modules/update/update.manager.inc
+++ b/core/modules/update/update.manager.inc
@@ -42,14 +42,6 @@
 use Symfony\Component\HttpFoundation\RedirectResponse;
 
 /**
- * @defgroup update_manager_update Update Manager module: update
- * @{
- * Update Manager module functionality for updating existing code.
- *
- * Provides a user interface to update existing code.
- */
-
-/**
  * Form constructor for the update form of the Update Manager module.
  *
  * This presents a table with all projects that have available updates with
@@ -285,7 +277,6 @@ function update_manager_update_form($form, $form_state = array(), $context) {
  *   An associative array containing:
  *   - form: A render element representing the form.
  *
- * @ingroup themeable
  */
 function theme_update_manager_update_form($variables) {
   $form = $variables['form'];
@@ -485,18 +476,6 @@ function update_manager_update_ready_form_submit($form, &$form_state) {
 }
 
 /**
- * @} End of "defgroup update_manager_update".
- */
-
-/**
- * @defgroup update_manager_install Update Manager module: install
- * @{
- * Update Manager module functionality for installing new code.
- *
- * Provides a user interface to install new code.
- */
-
-/**
  * Form constructor for the install form of the Update Manager module.
  *
  * This presents a place to enter a URL or upload an archive file to use to
@@ -761,19 +740,6 @@ function update_manager_install_form_submit($form, &$form_state) {
 }
 
 /**
- * @} End of "defgroup update_manager_install".
- */
-
-/**
- * @defgroup update_manager_file Update Manager module: file management
- * @{
- * Update Manager module file management functions.
- *
- * These functions are used by the update manager to copy, extract, and verify
- * archive files.
- */
-
-/**
  * Unpacks a downloaded archive file.
  *
  * @param string $file
@@ -953,7 +919,3 @@ function update_manager_local_transfers_allowed() {
 
   return $local_transfers_allowed;
 }
-
-/**
- * @} End of "defgroup update_manager_file".
- */