Fix typos and broken link in ui/README (kubeflow#1014)

Signed-off-by: manaswinidas <[email protected]>

Author: manaswinidas

README.md

@@ -154,12 +154,12 @@ When shutting down the docker compose, you might want to clean-up the SQLite db
 
 ### Testing architecture
 
-The following diagram illustrate testing strategy for the several components in Model Registry project:
+The following diagram illustrates testing strategy for the several components in Model Registry project:
 
 ![](/docs/Model%20Registry%20Testing%20areas.png)
 
 Go layers components are tested with Unit Tests written in Go, as well as Integration Tests leveraging Testcontainers.
-This allows to verify the expected "Core layer" of logical data mapping developed implemented in Go, matches technical expectations.
+This allows to verify the expected "Core layer" of logical data mapping developed and implemented in Go, matches technical expectations.
 
 Python client is also tested with Unit Tests and Integration Tests written in Python.
 
@@ -175,13 +175,13 @@ To delete something, simply update its status.
 ## Tips
 ### Pull image rate limiting
 
-Ocassionally you may encounter an 'ImagePullBackOff' error when deploying the Model Registry manifests. See example below for the `model-registry-db` container.
+Occasionally you may encounter an 'ImagePullBackOff' error when deploying the Model Registry manifests. See example below for the `model-registry-db` container.
 
 ```
 Failed to pull image “mysql:8.3.0”: rpc error: code = Unknown desc = fetching target platform image selected from image index: reading manifest sha256:f9097d95a4ba5451fff79f4110ea6d750ac17ca08840f1190a73320b84ca4c62 in docker.io/library/mysql: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
 ```
 
-This error is triggered by the rate limits from docker.io; in this example specifically about the image `mysql:8.3.0` (the expanded reference is `docker.io/library/mysql:8.3.0`). To mitigate against this error you could [authenticate using image pull secrets](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) for _local development_; or replace the image used with alternative mirrored images, for instance with the following example:
+This error is triggered by the rate limits from docker.io; in this example specifically about the image `mysql:8.3.0` (the expanded reference is `docker.io/library/mysql:8.3.0`). To mitigate this error you could [authenticate using image pull secrets](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) for _local development_; or replace the image used with alternative mirrored images, for instance with the following example:
 ```
 manifests/kustomize/overlays/db/model-registry-db-deployment.yaml file.
 

clients/ui/README.md

@@ -1,7 +1,7 @@
 [frontend requirements]: ./frontend/docs/dev-setup.md#requirements
 [BFF requirements]: ./bff/README.md#pre-requisites
 [Model registry UI]: ./docs/README.md
-[contributing guidelines]: ../CONTRIBUTING.md
+[contributing guidelines]: ./CONTRIBUTING.md
 
 # Model Registry UI
 

docs/logical_model.md

@@ -225,7 +225,7 @@ curl --silent -X 'GET' \
 }
 ```
 
-A ML model from S3 bucket with all required location details except of credentials:
+A ML model from S3 bucket with all required location details except credentials:
 
 ```python
 model = registry.register_model(

docs/mr_kind_deploy_ingress.md

@@ -90,4 +90,4 @@ Run `curl http://model-registry.io:3080/api/model_registry/v1alpha3/registered_m
 
 ## Teardown
 
-kind delete cluster
+`kind delete cluster`