Corrected spelling and grammar errors.

:summary: Announce a new tool, bundle_certs

Like I said in a previous blog post, I rarely blog but I run :code:`git init

project-name` like crazy. So here's a new such repo, `bundle_certs

project-name` pretty regularly. So here's a new such repo, `bundle_certs

<https://www.shore.co.il/cgit/bundle_certs/>`_. A simple shell script for

bundling (in correct order) SSL certificates.

bundling (in the correct order) SSL certificates.

How I start new projects

------------------------

how I use them and this seems like a good opportunity to share. First of all I

keep my rc files (like :code:`.vimrc`) in the

`rcfiles <https://www.shore.co.il/cgit/rcfiles/`>_ repo. However I don't install

as mentioned in the documentation. Instead I add as Git submodules and now I 

can be reasonably sure that when I clone the rcfiles repository, the aliases and

sourced files mentioned in :code:`.bashrc` are present. Here's how:

them as mentioned in the documentation. Instead I add them as Git submodules

and now I can be reasonably sure that when I clone the rcfiles repository, the

aliases and sourced files mentioned in :code:`.bashrc` are present. Here's how:

.. code:: shell

and git hooks). 

Another option I know of are tools that manage a specific aspect of the repo,

for example the license, or :code:`.gitignore`. A third option is using a

project management tool like `Cargo <http://doc.crates.io/>`_ for Rust or

`Leiningen <http://leiningen.org/>`_ for Clojure. But not all aspects or

languages have such tools.

for example the license, or :code:`.gitignore`.

A third option is using a project management tool like `Cargo

<http://doc.crates.io/>`_ for Rust or `Leiningen <http://leiningen.org/>`_

for Clojure. But not all aspects or languages have such tools.

The fourth option I'm thinking of is using a scaffloding tool, mainly `Yeoman

<http://yeoman.io/>`_ as it seems to the most popular one but its focus is on