diff --git a/console/calling_commands.rst b/console/calling_commands.rst
index 2defb04d49a..001dc47e35e 100644
--- a/console/calling_commands.rst
+++ b/console/calling_commands.rst
@@ -58,6 +58,6 @@ method)::
 
 .. note::
 
-    Most of the times, calling a command from code that is not executed on the
+    Most of the time, calling a command from code that is not executed on the
     command line is not a good idea. The main reason is that the command's
     output is optimized for the console and not to be passed to other commands.
diff --git a/profiler.rst b/profiler.rst
index 42e925b89c8..1cce51d75cd 100644
--- a/profiler.rst
+++ b/profiler.rst
@@ -35,10 +35,19 @@ Symfony Profiler, which will look like this:
     in the ``X-Debug-Token-Link`` HTTP response header. Browse the ``/_profiler``
     URL to see all profiles.
 
+.. versionadded:: 6.3
+
+    Profile garbage collection was introduced in Symfony 6.3.
+
+.. note::
+
+    To limit the storage used by profiles on disk, they are probabilistically
+    removed after 2 days.
+
 Accessing Profiling Data Programmatically
 -----------------------------------------
 
-Most of the times, the profiler information is accessed and analyzed using its
+Most of the time, the profiler information is accessed and analyzed using its
 web-based interface. However, you can also retrieve profiling information
 programmatically thanks to the methods provided by the ``profiler`` service.