_includes/home/secondary.html: generic push advice

As suggested in git-lfs/git-lfs#5909, now that our project home page
is generic, our instructions should be fully generic as well, so we
remove the legacy suggestion to specifically push to GitHub.

Author: chrisd8088

_includes/home/secondary.html

@@ -29,7 +29,7 @@ <h2 class="section-heading">Getting Started</h2>
           <p>Note that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. To do that, use the <a href="https://github.com/git-lfs/git-lfs/blob/main/docs/man/git-lfs-migrate.adoc?utm_source=gitlfs_site&amp;utm_medium=doc_man_migrate_link&amp;utm_campaign=gitlfs">git lfs migrate(1)</a> command, which has a range of options designed to suit various potential use cases.</p>
         </li>
         <li>
-          <p>There is no step three. Just commit and push to GitHub as you normally would; for instance, if your current branch is named <code>main</code>:</p>
+          <p>There is no step three. Just commit and push as you normally would; for instance, if your current branch is named <code>main</code>:</p>
 <pre>
 git add file.psd
 git commit -m "Add design file"