Merge pull request #992 from vespa-engine/kkraune/misc

Kkraune/misc

docs/sphinx/source/authenticating-to-vespa-cloud.ipynb

@@ -885,7 +885,7 @@
                 "\n",
                 "It is often overlooked that all interactions with Vespa are through HTTP-api calls, so you are free to use any HTTP client you like.\n",
                 "\n",
-                "Below is an example of how to use the `requests` library to interact with Vespa, using `key` and `cert` for authentication, and the [`/document/v1/`](https://docs.vespa.ai/en/reference/document-v1-api-reference.html) endpoint to feed data to Vespa.\n"
+                "Below is an example of how to use the `requests` library to interact with Vespa, using `key` and `cert` for authentication, and the [/document/v1/](https://docs.vespa.ai/en/reference/document-v1-api-reference.html) endpoint to feed data to Vespa.\n"
             ]
         },
         {

docs/sphinx/source/examples/feed_performance.ipynb

@@ -2184,9 +2184,9 @@
             "source": [
                 "Interesting. Let's try to summarize the insights we got from this experiment:\n",
                 "\n",
-                "- The `feed_sync` method is the slowest, and does not benefit much from increasing 'max_connections'.\n",
+                "- The `feed_sync` method is the slowest, and does not benefit much from increasing `max_connections`.\n",
                 "  As there is no concurrency, and each request is blocking, this will be bound by the network latency, which in many cases will be a lot higher than when running against a local VespaDocker instance. For example, if you have 100ms latency against your Vespa instance, you can only feed 10 documents per second using the `VespaSync` method.\n",
-                "- The `feed_async` method is the fastest, and benefits slightly from increasing 'max_connections' regardless of the number of documents. This method is non-blocking, and will likely be even more beneficial when running against a remote Vespa instance, such as [Vespa Cloud](https://cloud.vespa.ai/), when network latency is higher.\n",
+                "- The `feed_async` method is the fastest, and benefits slightly from increasing `max_connections` regardless of the number of documents. This method is non-blocking, and will likely be even more beneficial when running against a remote Vespa instance, such as [Vespa Cloud](https://cloud.vespa.ai/), when network latency is higher.\n",
                 "- The `feed_iterable` performance is somewhere in between the other two methods, and benefits a lot from increasing `num_workers` when the number of documents increases.\n",
                 "\n",
                 "We have not looked at multiprocessing, but there is definitively room to utilize more cores to improve further upon these results.\n",
@@ -3742,4 +3742,4 @@
     },
     "nbformat": 4,
     "nbformat_minor": 5
-}
+}