diff -u b/core/core.api.php b/core/core.api.php
--- b/core/core.api.php
+++ b/core/core.api.php
@@ -2484,7 +2484,7 @@
  * of the system to interact and communicate with each other. Each event has a
  * unique string name. One system component dispatches the event at an
  * appropriate time; many events are dispatched by Drupal core and the Symfony
- * event system in every request. Other system components can register as event
+ * framework in every request. Other system components can register as event
  * subscribers; when an event is dispatched, a method is called on each
  * registered subscriber, allowing each one to react. For more on the general
  * concept of events, see
@@ -2497,14 +2497,13 @@
  * Overview of event dispatch and subscribing
  *
  * @section sec_intro Introduction and terminology
- * Events are part of the Symfony framework: they allow for different components
- * of the system to interact and communicate with each other. Each event has a
- * unique string name. One system component dispatches the event at an
- * appropriate time; many events are dispatched by Drupal core and the Symfony
- * framework in every request. Other system components can register as event
- * subscribers; when an event is dispatched, a method is called on each
- * registered subscriber, allowing each one to react. For more on the general
- * concept of events, see
+ * Events allow different components of the system to interact and communicate
+ * with each other. Each event has a unique string name. One system component
+ * dispatches the event at an  appropriate time; many events are dispatched by
+ * Drupal core and the Symfony event system in every request. Other system
+ * components can register as event subscribers; when an event is dispatched, a
+ * method is called on each registered subscriber, allowing each one to react.
+ * For more on the general concept of events, see
  * http://symfony.com/doc/current/components/event_dispatcher/introduction.html
  *
  * @section sec_dispatch Dispatching events
only in patch2:
unchanged:
--- a/core/lib/Drupal/Core/Routing/routing.api.php
+++ b/core/lib/Drupal/Core/Routing/routing.api.php
@@ -13,7 +13,7 @@
  * @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
+ * @link http://symfony.com Symfony routing system. @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
@@ -65,7 +65,7 @@
  *   - _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
+ *   instructions (it has other uses in the Symfony components). 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.