diff --git a/scipost/templates/scipost/PlanSciPost.html b/scipost/templates/scipost/PlanSciPost.html
index b9b0b1c04b9db616cd79958db7bca84cf4417dcd..a0c470e5f6d1bb9a589ebbbd23be07bfb27f3363 100644
--- a/scipost/templates/scipost/PlanSciPost.html
+++ b/scipost/templates/scipost/PlanSciPost.html
@@ -27,7 +27,7 @@
     <p class="ml-2 mr-2">The general architecture is illustrated as follows:</p>
     <p><img style="max-width: 600px;" src="{% static 'scipost/2018_10_SciPost_Journals_plan.png' %}"></img></p>
 
-    <p class="ml-2 mr-2">Within a given field, the set of journal titles is designed to respond to and serve field-specific needs (see the example of our family of <a href="{% url 'journals:journals' %}#physics">Physics Journals</a>). Each Journal must however follow our open peer-witnessed refereeing workflow and general Editorial College-based procedures. Moreover, each field is to feature a field-leading title mirroring our pioneering Journal <a href="{% url 'journal:about' 'SciPostPhys' %}">SciPost Physics</a> (and in particular implementing promotion of selected extended abstracts for publication in <a href="{% url 'journals:journals' %}#selections">SciPost Selections</a>).</p>
+    <p class="ml-2 mr-2">Within a given field, the set of journal titles is designed to respond to and serve field-specific needs (see the example of our family of <a href="{% url 'journals:journals' %}#physics">Physics Journals</a>). Each Journal must however follow our open peer-witnessed refereeing workflow and general Editorial College-based procedures. Moreover, each field is to feature a field-leading title mirroring our pioneering Journal <a href="{% url 'journal:about' 'SciPostPhys' %}">SciPost Physics</a> (and in particular implementing promotion of selected extended abstracts for publication in {#<a href="{% url 'journals:journals' %}#selections">#}SciPost Selections{#</a>#}).</p>
 
     <h3>Current situation and triggers for expansion</h3>
     <p class="ml-2 mr-2 mt-2">