From 6dde48c77738070e1f8ec3b6afdad3158677821d Mon Sep 17 00:00:00 2001
From: Dylan Russell <dylanrussell@google.com>
Date: Tue, 4 Feb 2025 21:14:31 +0000
Subject: [PATCH] Add space to logging exporter README. Make minor update to
 releasing.md.

---
 docs/releasing.md                             | 13 ++-----------
 opentelemetry-exporter-gcp-logging/README.rst |  1 +
 2 files changed, 3 insertions(+), 11 deletions(-)

diff --git a/docs/releasing.md b/docs/releasing.md
index aa6a9f46..7d4bda63 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -89,17 +89,8 @@ with:
 **pointing at the first commit (a)** that was merged into main. For the
 example PR listed above, that creates release
 [`v0.11b0@4ad9ccd`](https://github.com/GoogleCloudPlatform/opentelemetry-operations-python/releases/tag/v0.11b0).
-- In description, paste a changelog for the packages. I used this (probably
-buggy) small script for the example PR's tag:
-
-  ```bash
-  for cl in opentelemetry-*/CHANGELOG.md; do
-      if cl_entries=`pcregrep -M -o1 "^## Version 0\.10b0$\n\n^Released.*\n\n((?:- [\s\S]+?)*?)(?=(\s+##|\Z))" $cl`
-      then
-          echo -e "# `dirname $cl`\n$cl_entries"
-      fi
-  done
-  ```
+
+Click the "Generate release notes" button in the UI to get an autogenerated changelog for the packages.
 
 Once the release tag is created, move the `stable` tag to point to the same
 commit.
diff --git a/opentelemetry-exporter-gcp-logging/README.rst b/opentelemetry-exporter-gcp-logging/README.rst
index 9fa6a4d9..89fa70be 100644
--- a/opentelemetry-exporter-gcp-logging/README.rst
+++ b/opentelemetry-exporter-gcp-logging/README.rst
@@ -35,6 +35,7 @@ Usage
 -----
 
 .. code:: python
+
     import logging
     from opentelemetry.exporter.cloud_logging import (
         CloudLoggingExporter,