Skip to content

Commit 47c1986

Browse files
committed
Fixed some wrong links to external API classes/methods
1 parent 4d8c866 commit 47c1986

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

components/cache/cache_pools.rst

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ Saving Cache Items
6969
------------------
7070

7171
The most common method to save cache items is
72-
:method:`Psr\\Cache\\CacheItemPoolInterface::save`, which stores the
72+
``Psr\\Cache\\CacheItemPoolInterface::save``, which stores the
7373
item in the cache immediately (it returns ``true`` if the item was saved or
7474
``false`` if some error occurred)::
7575

@@ -80,9 +80,9 @@ item in the cache immediately (it returns ``true`` if the item was saved or
8080

8181
Sometimes you may prefer to not save the objects immediately in order to
8282
increase the application performance. In those cases, use the
83-
:method:`Psr\\Cache\\CacheItemPoolInterface::saveDeferred` method to mark cache
83+
``Psr\\Cache\\CacheItemPoolInterface::saveDeferred`` method to mark cache
8484
items as "ready to be persisted" and then call to
85-
:method:`Psr\\Cache\\CacheItemPoolInterface::commit` method when you are ready
85+
``Psr\\Cache\\CacheItemPoolInterface::commit`` method when you are ready
8686
to persist them all::
8787

8888
// ...
@@ -103,22 +103,22 @@ Removing Cache Items
103103
--------------------
104104

105105
Cache Pools include methods to delete a cache item, some of them or all of them.
106-
The most common is :method:`Psr\\Cache\\CacheItemPoolInterface::deleteItem`,
106+
The most common is ``Psr\\Cache\\CacheItemPoolInterface::deleteItem``,
107107
which deletes the cache item identified by the given key (it returns ``true``
108108
when the item is successfully deleted or doesn't exist and ``false`` otherwise)::
109109

110110
// ...
111111
$isDeleted = $cache->deleteItem('user_'.$userId);
112112

113-
Use the :method:`Psr\\Cache\\CacheItemPoolInterface::deleteItems` method to
113+
Use the ``Psr\\Cache\\CacheItemPoolInterface::deleteItems`` method to
114114
delete several cache items simultaneously (it returns ``true`` only if all the
115115
items have been deleted, even when any or some of them don't exist)::
116116

117117
// ...
118118
$areDeleted = $cache->deleteItems(array('category1', 'category2'));
119119

120120
Finally, to remove all the cache items stored in the pool, use the
121-
:method:`Psr\\Cache\\CacheItemPoolInterface::clear` method (which returns ``true``
121+
``Psr\\Cache\\CacheItemPoolInterface::clear`` method (which returns ``true``
122122
when all items are successfully deleted)::
123123

124124
// ...
@@ -157,7 +157,7 @@ Pruning Cache Items
157157
Some cache pools do not include an automated mechanism for pruning expired cache items.
158158
For example, the :ref:`FilesystemAdaper <component-cache-filesystem-adapter>` cache
159159
does not remove expired cache items *until an item is explicitly requested and determined to
160-
be expired*, for example, via a call to :method:`Psr\\Cache\\CacheItemPoolInterface::getItem`.
160+
be expired*, for example, via a call to ``Psr\\Cache\\CacheItemPoolInterface::getItem``.
161161
Under certain workloads, this can cause stale cache entries to persist well past their
162162
expiration, resulting in a sizable consumption of wasted disk or memory space from excess,
163163
expired cache items.

reference/configuration/framework.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1909,7 +1909,7 @@ The name of the adapter to use. You could also use your own implementation.
19091909

19101910
.. note::
19111911

1912-
Your service MUST implement the :class:`Psr\\Cache\\CacheItemPoolInterface` interface.
1912+
Your service MUST implement the ``Psr\\Cache\\CacheItemPoolInterface`` interface.
19131913

19141914
public
19151915
""""""

0 commit comments

Comments
 (0)