all: fix spelling errors

2 files changed, 2 insertions, 2 deletions

diff --git a/swarm/storage/netstore.go b/swarm/storage/netstore.go
index 334229aed..f97862bbb 100644
--- a/swarm/storage/netstore.go
+++ b/swarm/storage/netstore.go
@@ -99,7 +99,7 @@ func (self *NetStore) Put(entry *Chunk) {
 	// handle deliveries
 	if entry.Req != nil {
 		glog.V(logger.Detail).Infof("NetStore.Put: localStore.Put %v hit existing request...delivering", entry.Key.Log())
-		// closing C singals to other routines (local requests)
+		// closing C signals to other routines (local requests)
 		// that the chunk is has been retrieved
 		close(entry.Req.C)
 		// deliver the chunk to requesters upstream
diff --git a/swarm/storage/types.go b/swarm/storage/types.go
index c36522012..f3ab99c6c 100644
--- a/swarm/storage/types.go
+++ b/swarm/storage/types.go
@@ -177,7 +177,7 @@ It relies on the underlying chunking model.
 When calling Split, the caller provides a channel (chan *Chunk) on which it receives chunks to store. The DPA delegates to storage layers (implementing ChunkStore interface).
 
 Split returns an error channel, which the caller can monitor.
-After getting notified that all the data has been split (the error channel is closed), the caller can safely read or save the root key. Optionally it times out if not all chunks get stored or not the entire stream of data has been processed. By inspecting the errc channel the caller can check if any explicit errors (typically IO read/write failures) occured during splitting.
+After getting notified that all the data has been split (the error channel is closed), the caller can safely read or save the root key. Optionally it times out if not all chunks get stored or not the entire stream of data has been processed. By inspecting the errc channel the caller can check if any explicit errors (typically IO read/write failures) occurred during splitting.
 
 When calling Join with a root key, the caller gets returned a seekable lazy reader. The caller again provides a channel on which the caller receives placeholder chunks with missing data. The DPA is supposed to forward this to the chunk stores and notify the chunker if the data has been delivered (i.e. retrieved from memory cache, disk-persisted db or cloud based swarm delivery). As the seekable reader is used, the chunker then puts these together the relevant parts on demand.
 */