Site updated at 2019-07-12 16:22:07 UTC

rakaramos · rakaramos · commit 0677b380b6e6 · 2019-07-12T13:22:07.000-03:00
diff --git a/atom.xml b/atom.xml
@@ -4,7 +4,7 @@
   <title><![CDATA[NSHint]]></title>
   <link href="http://nshint.github.io/atom.xml" rel="self"/>
   <link href="http://nshint.github.io/"/>
-  <updated>2019-07-12T13:15:49-03:00</updated>
+  <updated>2019-07-12T13:21:51-03:00</updated>
   <id>http://nshint.github.io/</id>
   <author>
     <name><![CDATA[NSHint]]></name>
@@ -110,7 +110,7 @@ Wrapping up the fields in <code>Optional</code>, may loosen its strictness.</p>
 
 <p>From a domain perspective, that <code>return</code> doesn&rsquo;t make any sense.</p>
 
-<p>One could argue that it&rsquo;s &ldquo;save&rdquo; to force unwrap in this case, or that there are <a href="https://www.swiftbysundell.com/posts/handling-non-optional-optionals-in-swift">already a nice approach to this problem</a>.</p>
+<p>One could argue that it&rsquo;s &ldquo;safe&rdquo; to force unwrap in this case, or that there is <a href="https://www.swiftbysundell.com/posts/handling-non-optional-optionals-in-swift">already a nice approach to this problem</a>.</p>
 
 <p>One may say, <em>&ldquo;we can raise an error to the user&rdquo;</em> or <em>&ldquo;we could track it and check if users are getting stuck somehow&rdquo;</em>. But, at the end of the day, this is not a good solution because you know that when the flow ends, you have all the values.</p>
 
diff --git a/blog/2019/07/15/complete-flows-partial-models/index.html b/blog/2019/07/15/complete-flows-partial-models/index.html
@@ -189,7 +189,7 @@ <h1 class="entry-title">Complete Flows, Partial Models</h1>
 
 <p>From a domain perspective, that <code>return</code> doesn&rsquo;t make any sense.</p>
 
-<p>One could argue that it&rsquo;s &ldquo;save&rdquo; to force unwrap in this case, or that there are <a href="https://www.swiftbysundell.com/posts/handling-non-optional-optionals-in-swift">already a nice approach to this problem</a>.</p>
+<p>One could argue that it&rsquo;s &ldquo;safe&rdquo; to force unwrap in this case, or that there is <a href="https://www.swiftbysundell.com/posts/handling-non-optional-optionals-in-swift">already a nice approach to this problem</a>.</p>
 
 <p>One may say, <em>&ldquo;we can raise an error to the user&rdquo;</em> or <em>&ldquo;we could track it and check if users are getting stuck somehow&rdquo;</em>. But, at the end of the day, this is not a good solution because you know that when the flow ends, you have all the values.</p>
 
diff --git a/sitemap.xml b/sitemap.xml
@@ -113,10 +113,4 @@
   <url>
     <loc>http://nshint.github.io/team/</loc>
   </url>
-  <url>
-    <loc>http://nshint.github.io/posts/2/</loc>
-  </url>
-  <url>
-    <loc>http://nshint.github.io/posts/3/</loc>
-  </url>
 </urlset>
