Merge pull request #148 from flipt-io/gm/gitops-guide-repo

chore(guides): add link to forkable example repo

guides/get-going-with-gitops.mdx

@@ -39,6 +39,11 @@ While we feel confident in our implementation, we're going to practice caution a
 
 ### The Application
 
+<Note>
+  If you want to follow along you can fork our [gitops guide
+  repository](https://github.com/flipt-io/flipt-gitops-guide).
+</Note>
+
 ```bash
 .
 ├── go.mod
@@ -235,6 +240,13 @@ git push origin main
 Once Flipt has received the updated reference, our flag should be available through Flipt's API.
 The code change we added can now safely reference the present flag, which is currently in a `disabled` state.
 
+This is where you would use `curl` to ensure the service is still behaving as expected:
+
+```bash
+# the -w option prints timing output at the end
+curl -w "\nTotal: %{time_total}s\n" "http://localhost:8000/words"
+```
+
 Next we will begin to enable the flag under different conditions.
 
 ## Targeting and Rollouts
@@ -337,6 +349,10 @@ Whereas, the rest of users should still be served using the old Bubble Sort algo
   entries. You can fix those changes now before targeting more users.
 </Tip>
 
+```bash
+curl -w "\nTotal: %{time_total}s\n" "http://localhost:8000/words?org=internal-users"
+```
+
 ### Proportional Rollout
 
 Once we're confident our change is working as expected, since we've validated the change in production for `internal` users, we can start to roll it out to external users.
@@ -476,7 +492,7 @@ At each commit, we could've fully recreated the configuration of our entire appl
 Now you have all the tools necessary to practice GitOps with your feature flags.
 
 However, in production, your mileage may vary with the different backed types.
-You might want to consider the `object` (and AWS S3 type) backend if your source Git repositories are large (we're working on a guide for that now).
+You might want to consider the `object` (and AWS S3 type) or the `oci` backend if your source Git repositories are large (we're working on a guide for that now).
 
 The declarative storage backends currently mandate that the UI is **read-only**.
 We've thoughts on how this could change in the future, but for now, this is a limitation.