mirror of
https://github.com/odoo/documentation.git
synced 2025-12-17 09:59:15 +07:00
[FIX] content/developer/*: typos
Found with codespell
This commit is contained in:
@@ -10,7 +10,7 @@ Profiling Odoo code
|
||||
Graph a method
|
||||
==============
|
||||
|
||||
Odoo embeds a profiler of code. This embeded profiler output can be used to
|
||||
Odoo embeds a profiler of code. This embedded profiler output can be used to
|
||||
generate a graph of calls triggered by the method, number of queries, percentage
|
||||
of time taken in the method itself as well as the time that the method took and
|
||||
its sub-called methods.
|
||||
@@ -85,7 +85,7 @@ Dump stack
|
||||
|
||||
Sending the SIGQUIT signal to an Odoo process (only available on POSIX) makes
|
||||
this process output the current stack trace to log, with info level. When an
|
||||
odoo process seems stucked, sending this signal to the process permit to know
|
||||
odoo process seems stuck, sending this signal to the process permit to know
|
||||
what the process is doing, and letting the process continue his job.
|
||||
|
||||
Tracing code execution
|
||||
|
||||
@@ -394,7 +394,7 @@ So here are the steps to create a robust and consistent style for your theme:
|
||||
|
||||
\(1) Set the values for Odoo-provided SCSS variables
|
||||
|
||||
Odoo declares many CSS rules, most being entirely customizable by overridding
|
||||
Odoo declares many CSS rules, most being entirely customizable by overriding
|
||||
the related SCSS variables. First, create a new file called primary_variables.scss
|
||||
and add it the same way as the style.scss file. The only difference it that
|
||||
you won't add it in the ``assets_frontend`` template but in the ``_assets_primary_variables``
|
||||
|
||||
@@ -1782,7 +1782,7 @@ When a client action must be executed, the action manager looks up its tag
|
||||
in the registry, walks the specified path and displays the widget it finds at
|
||||
the end.
|
||||
|
||||
.. note:: a client action handler can also be a regular function, in whch case
|
||||
.. note:: a client action handler can also be a regular function, in which case
|
||||
it'll be called and its result (if any) will be interpreted as the
|
||||
next action to execute.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user