summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--docs/users_guide/8.0.2-notes.rst2
-rw-r--r--docs/users_guide/eventlog-formats.rst16
-rw-r--r--docs/users_guide/profiling.rst6
3 files changed, 12 insertions, 12 deletions
diff --git a/docs/users_guide/8.0.2-notes.rst b/docs/users_guide/8.0.2-notes.rst
index 237c3b95ef..7c2e2d7883 100644
--- a/docs/users_guide/8.0.2-notes.rst
+++ b/docs/users_guide/8.0.2-notes.rst
@@ -171,7 +171,7 @@ Runtime system
`MSDN <https://msdn.microsoft.com/en-us/library/ms235384.aspx>`_ . This should now introduce the same
behavior both compiled and interpreted. (see :ghc-ticket:`12497`).
-- Profiles from the cost-center profiler now provide source span information.
+- Profiles from the cost-centre profiler now provide source span information.
(see :ghc-ticket:`11543`).
- The number of threads used for garbage collection is now configurable
diff --git a/docs/users_guide/eventlog-formats.rst b/docs/users_guide/eventlog-formats.rst
index 8d53f92323..f7eb1ca449 100644
--- a/docs/users_guide/eventlog-formats.rst
+++ b/docs/users_guide/eventlog-formats.rst
@@ -46,24 +46,24 @@ A single fixed-width event emitted during program start-up describing the sample
* ``String``: Retainer filter
* ``String``: Biography filter
-Cost center definitions
+Cost centre definitions
^^^^^^^^^^^^^^^^^^^^^^^
-A variable-length packet produced once for each cost center,
+A variable-length packet produced once for each cost centre,
* ``EVENT_HEAP_PROF_COST_CENTRE``
- * ``Word32``: cost center number
+ * ``Word32``: cost centre number
* ``String``: label
* ``String``: module
* ``String``: source location
* ``Word8``: flags
- * bit 0: is the cost-center a CAF?
+ * bit 0: is the cost-centre a CAF?
Sample event types
~~~~~~~~~~~~~~~~~~
-A sample (consisting of a list of break-down classes, e.g. cost centers, and
+A sample (consisting of a list of break-down classes, e.g. cost centres, and
heap residency sizes), is to be encoded in the body of one or more events.
We mark the beginning of a new sample with an ``EVENT_HEAP_PROF_SAMPLE_BEGIN``
@@ -78,17 +78,17 @@ in length a single sample may need to be split among multiple
determined by the break-down type.
-Cost-center break-down
+Cost-centre break-down
^^^^^^^^^^^^^^^^^^^^^^
A variable-length packet encoding a heap profile sample broken down by,
- * cost-center (``-hc``)
+ * cost-centre (``-hc``)
* ``EVENT_HEAP_PROF_SAMPLE_COST_CENTRE``
* ``Word8``: Profile ID
* ``Word64``: heap residency in bytes
* ``Word8``: stack depth
- * ``Word32[]``: cost center stack starting with inner-most (cost center numbers)
+ * ``Word32[]``: cost centre stack starting with inner-most (cost centre numbers)
String break-down
diff --git a/docs/users_guide/profiling.rst b/docs/users_guide/profiling.rst
index d035cc56d4..cf345ed513 100644
--- a/docs/users_guide/profiling.rst
+++ b/docs/users_guide/profiling.rst
@@ -419,11 +419,11 @@ enclosed between ``+RTS ... -RTS`` as usual):
.. rts-flag:: -po ⟨stem⟩
The :rts-flag:`-po` option overrides the stem used to form the output file
- paths for the cost-center profiler (see :rts-flag:`-p` and :rts-flag:`-pj`
+ paths for the cost-centre profiler (see :rts-flag:`-p` and :rts-flag:`-pj`
flags above) and heap profiler (see :rts-flag:`-h`).
For instance, running a program with ``+RTS -h -p -pohello-world`` would
- produce a heap profile named :file:`hello-world.hp` and a cost-center
+ produce a heap profile named :file:`hello-world.hp` and a cost-centre
profile named :file:`hello-world.prof`.
.. rts-flag:: -V <secs>
@@ -490,7 +490,7 @@ tree-like object (which we'll call a "cost-centre stack" here) with the
following properties,
``id`` (integral number)
- The ``id`` of a cost-center listed in the ``cost_centres`` list.
+ The ``id`` of a cost-centre listed in the ``cost_centres`` list.
``entries`` (integral number)
How many times was this cost-centre entered?
``ticks`` (integral number)