[lucene-solr-operator] branch main updated: Fix copy/paste typo addressed -> updated (#203)

[ho...@apache.org]

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

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


The following commit(s) were added to refs/heads/main by this push:
     new 2f4747c  Fix copy/paste typo addressed -> updated (#203)
2f4747c is described below

commit 2f4747cd436c629e6957dd9f3a12deb71fc8b7e8
Author: Jan Høydahl <ja...@users.noreply.github.com>
AuthorDate: Fri Jan 29 19:58:08 2021 +0100

    Fix copy/paste typo addressed -> updated (#203)
---
 docs/solr-cloud/solr-cloud-crd.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/solr-cloud/solr-cloud-crd.md b/docs/solr-cloud/solr-cloud-crd.md
index d6ac2af..494879f 100644
--- a/docs/solr-cloud/solr-cloud-crd.md
+++ b/docs/solr-cloud/solr-cloud-crd.md
@@ -38,7 +38,7 @@ These options can be found in `SolrCloud.spec.dataStorage`
 
 ## Update Strategy
 
-The SolrCloud CRD provides users the ability to define how it is addressed, through `SolrCloud.Spec.updateStrategy`.
+The SolrCloud CRD provides users the ability to define how Pod updates should be managed, through `SolrCloud.Spec.updateStrategy`.
 This provides the following options:
 
 Under `SolrCloud.Spec.updateStrategy`:
@@ -242,4 +242,4 @@ data:
     <solr>
      ... YOUR CUSTOM SOLR XML CONFIG HERE ...
     </solr>
-```
\ No newline at end of file
+```