diff --git a/docs/source/_templates/_static/css/ignite_theme.css b/docs/source/_templates/_static/css/ignite_theme.css
index 0eadd338bd2..1a4d967a9ad 100644
--- a/docs/source/_templates/_static/css/ignite_theme.css
+++ b/docs/source/_templates/_static/css/ignite_theme.css
@@ -143,3 +143,7 @@ article.pytorch-article table.longtable.docutils.align-default tbody td p {
   margin-block-start: 0.1em;
   margin-block-end: 0.1em;
 }
+
+article.pytorch-article div.highlight pre {
+  white-space: pre;
+}
diff --git a/docs/source/faq.rst b/docs/source/faq.rst
index 3fe334e5a67..4e4804b3a10 100644
--- a/docs/source/faq.rst
+++ b/docs/source/faq.rst
@@ -386,7 +386,7 @@ For details, see :class:`~ignite.engine.events.State`.
 
 
 Basic time profiling
-``````````````````
+````````````````````
 
 User can setup :class:`~ignite.contrib.handlers.time_profilers.BasicTimeProfiler` to fetch times spent in data
 processing, training step, event handlers:
@@ -447,7 +447,7 @@ For details, see :class:`~ignite.contrib.handlers.time_profilers.BasicTimeProfil
 
 
 Event handlers time profiling
-``````````````````
+`````````````````````````````
 
 If you want to get time breakdown per handler basis then you can setup
 :class:`~ignite.contrib.handlers.time_profilers.HandlersTimeProfiler`: