fidesctl -> fidesops [SOL-276]

docs/fidesops/docs/development/code_style.md

@@ -6,10 +6,10 @@
 
 Fides's code is formatted using the [black](https://github.com/ambv/black) style. This style is checked in a CI step, and merges to master are prevented if code does not conform.
 
-To apply black to your code, run black from the root Fidesctl directory:
+To apply black to your code, run black from the root Fidesops directory:
 
 ```bash
-cd fidesctl
+cd fidesops
 black .
 ```
 
@@ -19,10 +19,10 @@ A number of extensions are available for popular editors that will automatically
 
 Fides's code is linted using [pylint](https://pylint.org/). Linter checks run as part of a CI step and merges to master are prevented if code does not conform.
 
-To apply pylint to your code, run pylint from the root Fidesctl directory:
+To apply pylint to your code, run pylint from the root Fidesops directory:
 
 ```bash
-cd fidesctl
+cd fidesops
 pylint src
 ```
 
@@ -31,6 +31,6 @@ pylint src
 Fides's code is statically-typed using [mypy](http://mypy-lang.org/). Type checking is validated as a CI step, and merges to master are prevented if code does not pass type checks. As a general rule, mypy typing requires all function arguments and return values to be annotated.
 
 ```bash
-cd fidesctl
+cd fidesops
 mypy src
 ```

docs/fidesops/docs/development/testing.md

@@ -45,14 +45,14 @@ def test_dry_evaluate():
     ...
 ```
 
-Fides has a few [`pytest` fixtures](https://docs.pytest.org/en/stable/fixture.html) available for testing; see `conftest.py` for details.
+Fidesops has a few [`pytest` fixtures](https://docs.pytest.org/en/stable/fixture.html) available for testing; see `conftest.py` for details.
 
 ## Running tests
 
-Fides uses `pytest` for unit testing. To run tests, invoke `pytest` from the root Fides directory:
+Fidesops uses `pytest` for unit testing. To run tests, invoke `pytest` from the root Fidesops directory:
 
 ```bash
-cd fidesctl
+cd fidesops
 pytest
 ```