fix: Correcting broken and incorrect links

Author: timclegg

publishing/expectations.md

@@ -14,4 +14,4 @@ Before diving into getting a DevRel repo, here's what we ask (and expect) of you
 * Ideally there should be two or more maintainers for each repo (project). One person can't do everything (particularly the required code reviews), so having at least two maintainers is a very good idea.
 
 <br><br>
-[< [Where to Publish](where_to_publish.md) \| [Getting a Repository >](/publishing/getting_a_repo)
+[< Where to Publish](where_to_publish.md) \| [Standards >](/publishing/standards)

publishing/getting_a_repo.md

@@ -29,4 +29,4 @@ Don't work at Oracle, but have a great idea that you'd like to collaborate with
 The repo will come with public visibility, so there's nothing special to do to publish your work. You'll be set up as a maintainer (along with the other people you've requested as maintainers). From there, you're ready to [start working with your repo](/working_with_our_repos).
 
 <br><br>
-[< [Standards](standards.md) \| [Working With Our Repositories >](/working_with_our_repos)
+[< Standards](standards.md) \| [Working With Our Repositories >](/working_with_our_repos)

publishing/standards.md

@@ -29,7 +29,7 @@ We try to focus on being flexible and easy-to-use.  There is a minimum set of fi
 We expect the `.gitignore` file to ignore superfluous and extraneous "clutter" that's not necessary (things like hidden files that are not really needed, local caching files, etc.).  You'll likely need to adjust the `.github` file for the language(s) and framework(s) you'll be using in your project.  Customize away!
 
 # Branching
-We do not enforce a specific branching strategy, but leave it up to each project maintainer to dictate what's best for the project.  See [Working With Our Repos](/publishing/expectations) for more info.
+We do not enforce a specific branching strategy, but leave it up to each project maintainer to dictate what's best for the project.  See [Working With Our Repos](/publishing/working_with_repos) for more info.
 
 # Commit/PR Comments
 We prefer to standardize on using [ConventionalCommits](https://www.conventionalcommits.org/en/v1.0.0/) when generating change logs and creating comments on commits, PRs, etc.
@@ -38,7 +38,7 @@ We prefer to standardize on using [ConventionalCommits](https://www.conventional
 Most projects that contain source code (all but the text-only repos) are setup to be scanned by SonarCloud.io, along with a scanning status badge on the README.  Feel free to use (leave) this badge in-tact, as it's a nice marker to instill confidence in your code (or to encourage you to improve it).
 
 # Committing Code
-Do not commit directly to `main`.  It won't work anyway (`main` is protected).  Use Pull Requests (PRs) instead.  You can do this via a fork or branch.  If you're a maintainer, you can create a branch (you have permissions to do so).  If you're an outside contributor (or maintainer), you may fork the project (you don't have permissions to create a branch in the repo).  See [Working With Our Repos](/publishing/expectations) for more info.
+Do not commit directly to `main`.  It won't work anyway (`main` is protected).  Use Pull Requests (PRs) instead.  You can do this via a fork or branch.  If you're a maintainer, you can create a branch (you have permissions to do so).  If you're an outside contributor (or maintainer), you may fork the project (you don't have permissions to create a branch in the repo).  See [Working With Our Repos](/publishing/working_with_repos) for more info.
 
 <br><br>
-[< [What's Expected of You](/publishing/expectations) \| [Getting a Repository >](/publishing/getting_a_repo)
+[< What's Expected of You](/publishing/expectations) \| [Getting a Repository >](/publishing/getting_a_repo)

publishing/where_to_publish.md

@@ -17,4 +17,4 @@ Here's the "secret decoder ring" (of sorts) on where to publish:
 
 
 <br><br>
-[< Publishing](/publishing/) \| [What's Expected of You >](/publishing/expectations)
+[< Publishing](/publishing) \| [What's Expected of You >](/publishing/expectations)