@@ -110,7 +110,7 @@ the shared ``env`` object:
110110 * - `bus `
111111 - :ref: `main bus <frontend/framework/bus >`, used to coordinate some generic events
112112 * - `services `
113- - all deployed :ref: `services <javascript /services >` (should usually be accessed
113+ - all deployed :ref: `services <frontend /services >` (should usually be accessed
114114 with the `useService ` hook)
115115 * - `debug `
116116 - string. If non empty, the web client is in :ref: `debug mode <frontend/framework/debug_mode >`
@@ -144,11 +144,11 @@ services, components and hooks.
144144Registries
145145----------
146146
147- Registries are basically a simple key/value mapping that stores some specific
148- kind of objects. They are an important part of the extensibility of the UI:
149- once some object is registered, the rest of the web client can use it. For
150- example, the field registry contains all field components (or widgets) that
151- can be used in views.
147+ :ref: ` Registries < frontend/registries >` are basically a simple key/value mapping
148+ that stores some specific kind of objects. They are an important part of the
149+ extensibility of the UI: once some object is registered, the rest of the web
150+ client can use it. For example, the field registry contains all field components
151+ (or widgets) that can be used in views.
152152
153153.. code-block :: javascript
154154
@@ -166,12 +166,12 @@ sub registry ``fields``.
166166Services
167167--------
168168
169- Services are long lived pieces of code that provide a feature. They may be
170- imported by components (with ``useService ``) or by other services. Also, they
171- can declare a set of dependencies. In that sense, services are basically a DI
172- (dependency injection) system. For example, the ``notification `` service
173- provides a way to display a notification, or the ``rpc `` service is the proper
174- way to perform a request to the Odoo server.
169+ :ref: ` Services < frontend/services >` are long lived pieces of code that provide a
170+ feature. They may be imported by components (with ``useService ``) or by other
171+ services. Also, they can declare a set of dependencies. In that sense, services
172+ are basically a DI (dependency injection) system. For example, the ``notification ``
173+ service provides a way to display a notification, or the ``rpc `` service is the
174+ proper way to perform a request to the Odoo server.
175175
176176The following example registers a simple service that displays a notification
177177every 5 second:
@@ -195,7 +195,7 @@ every 5 second:
195195 Components and Hooks
196196--------------------
197197
198- Components and hooks are ideas coming from the
198+ :ref: ` Components < frontend/components >` and :ref: ` hooks < frontend/hooks >` are ideas coming from the
199199`Owl component system <https://github.com/odoo/owl/blob/master/doc/readme.md >`_.
200200Odoo components are simply owl components that are part of the web client.
201201
0 commit comments