[lucene-solr] branch master updated: Ref Guide: fix aliases.adoc TIP for proper conversion

[ct...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ctargett pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git


The following commit(s) were added to refs/heads/master by this push:
     new e9e2ff9  Ref Guide: fix aliases.adoc TIP for proper conversion
e9e2ff9 is described below

commit e9e2ff9b12d4934337aaf757539fba1a3015b387
Author: Cassandra Targett <ca...@lucidworks.com>
AuthorDate: Mon Jul 13 09:27:01 2020 -0500

    Ref Guide: fix aliases.adoc TIP for proper conversion
---
 solr/solr-ref-guide/src/aliases.adoc | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/solr/solr-ref-guide/src/aliases.adoc b/solr/solr-ref-guide/src/aliases.adoc
index 2bc268a..8b2c0a6 100644
--- a/solr/solr-ref-guide/src/aliases.adoc
+++ b/solr/solr-ref-guide/src/aliases.adoc
@@ -46,15 +46,18 @@ Alternatively this information is available by checking `/aliases.json` in ZooKe
 Aliases may be deleted via the <<collection-aliasing.adoc#deletealias,DELETEALIAS>> command.
 When deleting an alias, underlying collections are *unaffected*.
 
-TIP: Any alias (standard or routed) that references multiple collections may complicate relevancy.
+[TIP]
+====
+Any alias (standard or routed) that references multiple collections may complicate relevancy.
 By default, SolrCloud scores documents on a per-shard basis.
-+
+
 With multiple collections in an alias this is always a problem, so if you have a use case for which BM25 or
   TF/IDF relevancy is important you will want to turn on one of the
   <<distributed-requests.adoc#distributedidf,ExactStatsCache>> implementations.
-+
+
 However, for analytical use cases where results are sorted on numeric, date, or alphanumeric field values, rather
   than relevancy calculations, this is not a problem.
+====
 
 == Routed Aliases