fix grammar mistakes

Author: zhaobro

feed.xml

@@ -1,16 +1,16 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.2.0">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2021-09-17T13:21:12+08:00</updated><id>/feed.xml</id><title type="html">ZhaoCloud</title><entry><title type="html">Homepage Provider Changed</title><link href="/homepage-provider-changed" rel="alternate" type="text/html" title="Homepage Provider Changed" /><published>2021-09-16T00:00:00+08:00</published><updated>2021-09-16T00:00:00+08:00</updated><id>/homepage-provider-changed</id><content type="html" xml:base="/homepage-provider-changed">&lt;p&gt;My home page server is totally broken. In order to make it more stable. It’s hosted on GitHub now.&lt;/p&gt;
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.2.0">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2021-09-17T13:41:51+08:00</updated><id>/feed.xml</id><title type="html">ZhaoCloud</title><entry><title type="html">Homepage Provider Changed</title><link href="/homepage-provider-changed" rel="alternate" type="text/html" title="Homepage Provider Changed" /><published>2021-09-16T00:00:00+08:00</published><updated>2021-09-16T00:00:00+08:00</updated><id>/homepage-provider-changed</id><content type="html" xml:base="/homepage-provider-changed">&lt;p&gt;My home page server is totally broken. In order to make it more stable. It’s hosted on GitHub now.&lt;/p&gt;
 
 &lt;p&gt;repo: &lt;a href=&quot;https://github.com/ZhaoCloud-net/ZhaoCloud-net.github.io&quot;&gt;ZhaoCloud-net/ZhaoCloud-net.github.io&lt;/a&gt;&lt;/p&gt;</content><author><name></name></author><summary type="html">My home page server is totally broken. In order to make it more stable. It’s hosted on GitHub now.</summary></entry><entry><title type="html">Searx Update @2021.9.14</title><link href="/update-2021-09-14" rel="alternate" type="text/html" title="Searx Update @2021.9.14" /><published>2021-09-14T00:00:00+08:00</published><updated>2021-09-14T00:00:00+08:00</updated><id>/update-2021-09-14</id><content type="html" xml:base="/update-2021-09-14">&lt;p&gt;My server’s RAM isn’t enough. I gave up using Docker. And reinstalled Searx at all.&lt;/p&gt;
 
 &lt;p&gt;For normal users. You wouldn’t realize anything. Nothing changed for you.&lt;/p&gt;
 
-&lt;p&gt;But there’s one thing I must tell you. Today, I found something that maybe against my no-log policy. Some part of Searx, have the possibility to record log. Like Filtron, which protects my instance from bots, can record illegal requests after blocked them.&lt;/p&gt;
+&lt;p&gt;But there’s one thing I must tell you. Today, I found something that maybe against my no-log policy. Some parts of Searx, have the possibility to record log. Like Filtron, which protects my instance from bots, can record illegal requests after blocked them.&lt;/p&gt;
 
-&lt;p&gt;Especially, I’m running Searx in a new way. I’m not really sure that I used the best config. I need time to understand how everything working.&lt;/p&gt;
+&lt;p&gt;Especially, I’m running Searx in a new way. I’m not really sure that I’m using the best config. I need time to understand how everything working.&lt;/p&gt;
 
 &lt;p&gt;I don’t think your search and proxy logs are being recorded.&lt;/p&gt;
 
-&lt;p&gt;What I can promise to you is, I’m using 100%-pure Searx code. I don’t do anything bad on purpose.&lt;/p&gt;</content><author><name></name></author><summary type="html">My server’s RAM isn’t enough. I gave up using Docker. And reinstalled Searx at all.</summary></entry><entry><title type="html">DNSSEC and IPV6</title><link href="/dnssec-ipv6" rel="alternate" type="text/html" title="DNSSEC and IPV6" /><published>2021-08-13T00:00:00+08:00</published><updated>2021-08-13T00:00:00+08:00</updated><id>/dnssec-ipv6</id><content type="html" xml:base="/dnssec-ipv6">&lt;p&gt;Dnssec is enabled.&lt;/p&gt;
+&lt;p&gt;What I can promise to you is, this is 100%-pure Searx code. I don’t do anything bad on purpose.&lt;/p&gt;</content><author><name></name></author><summary type="html">My server’s RAM isn’t enough. I gave up using Docker. And reinstalled Searx at all.</summary></entry><entry><title type="html">DNSSEC and IPV6</title><link href="/dnssec-ipv6" rel="alternate" type="text/html" title="DNSSEC and IPV6" /><published>2021-08-13T00:00:00+08:00</published><updated>2021-08-13T00:00:00+08:00</updated><id>/dnssec-ipv6</id><content type="html" xml:base="/dnssec-ipv6">&lt;p&gt;Dnssec is enabled.&lt;/p&gt;
 
 &lt;p&gt;Ipv6 at Searx is disabled temporarily.&lt;/p&gt;</content><author><name></name></author><summary type="html">Dnssec is enabled.</summary></entry><entry><title type="html">Privacy Policy and Terms of Use v2</title><link href="/privacy-policy-and-terms-of-use210805" rel="alternate" type="text/html" title="Privacy Policy and Terms of Use v2" /><published>2021-08-05T00:00:00+08:00</published><updated>2021-08-05T00:00:00+08:00</updated><id>/privacy-policy-and-terms-of-use210805</id><content type="html" xml:base="/privacy-policy-and-terms-of-use210805">&lt;blockquote&gt;
   &lt;p&gt;main changes: &lt;br /&gt;- &lt;a href=&quot;https://zhaocloud.net/homepage-cdn&quot;&gt;Homepage with CDN&lt;/a&gt;&lt;/p&gt;

update-2021-09-14.html

@@ -52,13 +52,13 @@ <h1 class="post-title p-name" itemprop="name headline">Searx Update @2021.9.14</
 
 <p>For normal users. You wouldn’t realize anything. Nothing changed for you.</p>
 
-<p>But there’s one thing I must tell you. Today, I found something that maybe against my no-log policy. Some part of Searx, have the possibility to record log. Like Filtron, which protects my instance from bots, can record illegal requests after blocked them.</p>
+<p>But there’s one thing I must tell you. Today, I found something that maybe against my no-log policy. Some parts of Searx, have the possibility to record log. Like Filtron, which protects my instance from bots, can record illegal requests after blocked them.</p>
 
-<p>Especially, I’m running Searx in a new way. I’m not really sure that I used the best config. I need time to understand how everything working.</p>
+<p>Especially, I’m running Searx in a new way. I’m not really sure that I’m using the best config. I need time to understand how everything working.</p>
 
 <p>I don’t think your search and proxy logs are being recorded.</p>
 
-<p>What I can promise to you is, I’m using 100%-pure Searx code. I don’t do anything bad on purpose.</p>
+<p>What I can promise to you is, this is 100%-pure Searx code. I don’t do anything bad on purpose.</p>
 
   </div>